Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d45b096e1c15237ea9f799343231852404a0e716bdee29e79c79d80657a411de

Tx prefix hash: d02d64edde1e8b694c84eef90a34571782ce5235806b7c3c31b5bb3b637423d1
Tx public key: 7eef805d9e26e958316a42af9a031dcc3cf24711f5377a987cdf55acd480af24
Timestamp: 1748806977 Timestamp [UCT]: 2025-06-01 19:42:57 Age [y:d:h:m:s]: 00:173:04:43:44
Block: 1295831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121476 RingCT/type: yes/0
Extra: 017eef805d9e26e958316a42af9a031dcc3cf24711f5377a987cdf55acd480af24021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 294db97fd86ffe1580c3495fae8dc3b8fcc1c6e2cc5948e598a765dc9f9b55aa 0.600000000000 1783338 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": 1295841, "vin": [ { "gen": { "height": 1295831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "294db97fd86ffe1580c3495fae8dc3b8fcc1c6e2cc5948e598a765dc9f9b55aa" } } ], "extra": [ 1, 126, 239, 128, 93, 158, 38, 233, 88, 49, 106, 66, 175, 154, 3, 29, 204, 60, 242, 71, 17, 245, 55, 122, 152, 124, 223, 85, 172, 212, 128, 175, 36, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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