Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51b0a4391e9522d80a9ef31da8a1c4f5321733900794ec5035baec90eed0498c

Tx prefix hash: 5f6b972e467e43826998a4aaa7e7276b1df524b55e70b5478a817a8fddd2257d
Tx public key: ccd329d91f478a9fbefade3435f27616523a5e197695e03e3191e6bcfe720b29
Timestamp: 1577864335 Timestamp [UCT]: 2020-01-01 07:38:55 Age [y:d:h:m:s]: 05:302:23:56:56
Block: 36210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1364142 RingCT/type: yes/0
Extra: 01ccd329d91f478a9fbefade3435f27616523a5e197695e03e3191e6bcfe720b2902110000000fd81c26c0000000000000000000

1 output(s) for total of 465.662397568000 dcy

stealth address amount amount idx
00: 5f265d020feb0a50fba038926e20eea5bd1c247711e5d4c6859296bc6bfc212d 465.662397568000 61258 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": 36220, "vin": [ { "gen": { "height": 36210 } } ], "vout": [ { "amount": 465662397568, "target": { "key": "5f265d020feb0a50fba038926e20eea5bd1c247711e5d4c6859296bc6bfc212d" } } ], "extra": [ 1, 204, 211, 41, 217, 31, 71, 138, 159, 190, 250, 222, 52, 53, 242, 118, 22, 82, 58, 94, 25, 118, 149, 224, 62, 49, 145, 230, 188, 254, 114, 11, 41, 2, 17, 0, 0, 0, 15, 216, 28, 38, 192, 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