Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4b960e55cb63fa98dac4d112a1eeae29f3654b5afafa07e3763e14ebd2a48dc7

Tx prefix hash: bb54cdac1d79330eba1ff7b21267c7b0074b1029b2c658e6e5d1ee6d15a5b765
Tx public key: 734a2d9db510d12e9d4621783a311d8bcd9c10df77068d00f6e21e802704074a
Timestamp: 1708240484 Timestamp [UCT]: 2024-02-18 07:14:44 Age [y:d:h:m:s]: 01:116:01:15:32
Block: 960055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343977 RingCT/type: yes/0
Extra: 01734a2d9db510d12e9d4621783a311d8bcd9c10df77068d00f6e21e802704074a02110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b9034345d61e39d1231a5601b5543ef3151d4c7cb6c5f3f1432226c01ff5d16 0.600000000000 1419614 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 960065, "vin": [ { "gen": { "height": 960055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b9034345d61e39d1231a5601b5543ef3151d4c7cb6c5f3f1432226c01ff5d16" } } ], "extra": [ 1, 115, 74, 45, 157, 181, 16, 209, 46, 157, 70, 33, 120, 58, 49, 29, 139, 205, 156, 16, 223, 119, 6, 141, 0, 246, 226, 30, 128, 39, 4, 7, 74, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8