Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaf7ee7e25db50a8072f5904ebe0d78cc936fd5c5ab80bc227132e28e4d75ef0

Tx prefix hash: 22c17b7133f7f8e015996f996eb9b86ce506c5dd940eb243786188208ce8df6a
Tx public key: d6deaee32f19acbf61b8b863bdbaf2d579e2dbebc731ecb6e130803c152417f0
Timestamp: 1705031953 Timestamp [UCT]: 2024-01-12 03:59:13 Age [y:d:h:m:s]: 01:097:22:33:40
Block: 933441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331114 RingCT/type: yes/0
Extra: 01d6deaee32f19acbf61b8b863bdbaf2d579e2dbebc731ecb6e130803c152417f002110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9ffab5784ebc2066bb0106a540d6d9b27ccf5319f862e5430afc6ac12e5baa5 0.600000000000 1391403 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": 933451, "vin": [ { "gen": { "height": 933441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9ffab5784ebc2066bb0106a540d6d9b27ccf5319f862e5430afc6ac12e5baa5" } } ], "extra": [ 1, 214, 222, 174, 227, 47, 25, 172, 191, 97, 184, 184, 99, 189, 186, 242, 213, 121, 226, 219, 235, 199, 49, 236, 182, 225, 48, 128, 60, 21, 36, 23, 240, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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