Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a64bda73467a73e1342307769a9b0465ab68684a15e0356e7fc9ebb6b6aa99f9

Tx prefix hash: b9e27a369a2efc82690a333682fcbf47be486c6af479ef27d42c2698c7f03804
Tx public key: 119effdcd098909afb0ccdb1907bac2f4dcc643fa2241a3f39b16df3e190ef9f
Timestamp: 1577553832 Timestamp [UCT]: 2019-12-28 17:23:52 Age [y:d:h:m:s]: 05:011:20:34:43
Block: 33649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158561 RingCT/type: yes/0
Extra: 01119effdcd098909afb0ccdb1907bac2f4dcc643fa2241a3f39b16df3e190ef9f0211000000a6c3a1a09f000000000000000000

1 output(s) for total of 474.796765352000 dcy

stealth address amount amount idx
00: 3fc2ea707d762fdf5ada43ee50bf4d25c0c0c633c32cdb5502771822f07ac8ad 474.796765352000 56421 of 0

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": 33659, "vin": [ { "gen": { "height": 33649 } } ], "vout": [ { "amount": 474796765352, "target": { "key": "3fc2ea707d762fdf5ada43ee50bf4d25c0c0c633c32cdb5502771822f07ac8ad" } } ], "extra": [ 1, 17, 158, 255, 220, 208, 152, 144, 154, 251, 12, 205, 177, 144, 123, 172, 47, 77, 204, 100, 63, 162, 36, 26, 63, 57, 177, 109, 243, 225, 144, 239, 159, 2, 17, 0, 0, 0, 166, 195, 161, 160, 159, 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