Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 016d15036ab8d58b0658f69757e50c6dfcf4ea15da14ec82f873cbc02bd81406

Tx prefix hash: 92a2251932f039f34fa3870b9fbeff4d29035d34e4ea41f29ed367682ab7a8c6
Tx public key: 31ab76df024ea4ab81c76ce62f9ee4b66f2f68272d3416b68a3eec4d978dbeb4
Timestamp: 1739894431 Timestamp [UCT]: 2025-02-18 16:00:31 Age [y:d:h:m:s]: 00:274:16:00:58
Block: 1222022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194085 RingCT/type: yes/0
Extra: 0131ab76df024ea4ab81c76ce62f9ee4b66f2f68272d3416b68a3eec4d978dbeb40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 912ad1af1b30a09331a803cd48eb02730ee7dc5a899b5ca972997e9e7c1ac091 0.600000000000 1708869 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": 1222032, "vin": [ { "gen": { "height": 1222022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "912ad1af1b30a09331a803cd48eb02730ee7dc5a899b5ca972997e9e7c1ac091" } } ], "extra": [ 1, 49, 171, 118, 223, 2, 78, 164, 171, 129, 199, 108, 230, 47, 158, 228, 182, 111, 47, 104, 39, 45, 52, 22, 182, 138, 62, 236, 77, 151, 141, 190, 180, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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