Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 663cb423d6ae16e407fb2cdc54aec0e97442f39007327f333ff0e24b907a03cd

Tx prefix hash: 0c069d42861972d167c0aa6d4469ca74fc73ab49dfe048c3df871a7925e0ad26
Tx public key: df8121cdc27d68b1ebe8a72a28aba0fac824cbb16c2225259c8eb52c427891e2
Timestamp: 1671361845 Timestamp [UCT]: 2022-12-18 11:10:45 Age [y:d:h:m:s]: 02:182:11:37:51
Block: 655210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 652032 RingCT/type: yes/0
Extra: 01df8121cdc27d68b1ebe8a72a28aba0fac824cbb16c2225259c8eb52c427891e20211000000047e406890000000000000000000

1 output(s) for total of 4.140161270000 dcy

stealth address amount amount idx
00: 71557e232adf17b8f4c5c8e95d889d9ded82e0cb2d4d9e546bfeed155e6f0e44 4.140161270000 1095757 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": 655220, "vin": [ { "gen": { "height": 655210 } } ], "vout": [ { "amount": 4140161270, "target": { "key": "71557e232adf17b8f4c5c8e95d889d9ded82e0cb2d4d9e546bfeed155e6f0e44" } } ], "extra": [ 1, 223, 129, 33, 205, 194, 125, 104, 177, 235, 232, 167, 42, 40, 171, 160, 250, 200, 36, 203, 177, 108, 34, 37, 37, 156, 142, 181, 44, 66, 120, 145, 226, 2, 17, 0, 0, 0, 4, 126, 64, 104, 144, 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