Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5d20e7c9de4596a3ade93d1e3ccbfa4efe69c1af031edd0001062dc41020080

Tx prefix hash: d461cda3a6766a29ce6272b70e79a5263d235e1a2143991655b17b4a25f7da26
Tx public key: b48d4a7de8c44347199c4d26afd0a0b73a0d77746c902e57f5f297a47ea30636
Timestamp: 1709906117 Timestamp [UCT]: 2024-03-08 13:55:17 Age [y:d:h:m:s]: 01:037:18:43:54
Block: 973885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287994 RingCT/type: yes/0
Extra: 01b48d4a7de8c44347199c4d26afd0a0b73a0d77746c902e57f5f297a47ea306360211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d56098431aab38ff5de7d5942bc0c8ca8abceec4a3a24579d4754e909faad42b 0.600000000000 1433828 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": 973895, "vin": [ { "gen": { "height": 973885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d56098431aab38ff5de7d5942bc0c8ca8abceec4a3a24579d4754e909faad42b" } } ], "extra": [ 1, 180, 141, 74, 125, 232, 196, 67, 71, 25, 156, 77, 38, 175, 208, 160, 183, 58, 13, 119, 116, 108, 144, 46, 87, 245, 242, 151, 164, 126, 163, 6, 54, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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