Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8017b8427776b20b1039be546876cae7114653fe2aabce50922d08439d4eb41

Tx prefix hash: b663ce1a30b6e96dfc01cc6e9bb788f4616c1635f752abe0b443512bf2c479a0
Tx public key: e591b7f49854801d5e1b2dad563fd4393a6a2c7a2f70ef4a31120721e3df44bc
Timestamp: 1708900253 Timestamp [UCT]: 2024-02-25 22:30:53 Age [y:d:h:m:s]: 01:052:11:46:31
Block: 965537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298538 RingCT/type: yes/0
Extra: 01e591b7f49854801d5e1b2dad563fd4393a6a2c7a2f70ef4a31120721e3df44bc0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a53113c75844650d7244d05c18084b05bbcc4ebfd9b4b9471be4e60e5f28eaa0 0.600000000000 1425290 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": 965547, "vin": [ { "gen": { "height": 965537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a53113c75844650d7244d05c18084b05bbcc4ebfd9b4b9471be4e60e5f28eaa0" } } ], "extra": [ 1, 229, 145, 183, 244, 152, 84, 128, 29, 94, 27, 45, 173, 86, 63, 212, 57, 58, 106, 44, 122, 47, 112, 239, 74, 49, 18, 7, 33, 227, 223, 68, 188, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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