Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72095085735779e7f448a6434ad281c2eab6797256db9ff020b63c1b10131c49

Tx prefix hash: 4d153eabf7f34e11d251dd2cbc5e54c076c0e6a82ee70bdbc1a266b8afcaffec
Tx public key: 95dd51f4fb96d1e5e81fde8af9cf871e130be4c48b6250216efe50242b6a3e36
Timestamp: 1711151989 Timestamp [UCT]: 2024-03-22 23:59:49 Age [y:d:h:m:s]: 00:345:22:37:56
Block: 984221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247319 RingCT/type: yes/0
Extra: 0195dd51f4fb96d1e5e81fde8af9cf871e130be4c48b6250216efe50242b6a3e360211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f79398be9961c5394d1538c4cd6e4617dff2dff9ea627282bbaec4239723a3ea 0.600000000000 1444386 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": 984231, "vin": [ { "gen": { "height": 984221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f79398be9961c5394d1538c4cd6e4617dff2dff9ea627282bbaec4239723a3ea" } } ], "extra": [ 1, 149, 221, 81, 244, 251, 150, 209, 229, 232, 31, 222, 138, 249, 207, 135, 30, 19, 11, 228, 196, 139, 98, 80, 33, 110, 254, 80, 36, 43, 106, 62, 54, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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