Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1ac1efddf894ad13e2c1f1b75061a71abc4d35e1473596955e9196af31d6c11

Tx prefix hash: 016b893acaa559ed1ed0fedee17a88ae8560add3fa2837717e9dcf6e23613739
Tx public key: efc87981ce318c692b01bf7f5d3fd1bb9ed91d9105b28292c892aada3b570312
Timestamp: 1712701474 Timestamp [UCT]: 2024-04-09 22:24:34 Age [y:d:h:m:s]: 01:015:21:14:36
Block: 997026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272338 RingCT/type: yes/0
Extra: 01efc87981ce318c692b01bf7f5d3fd1bb9ed91d9105b28292c892aada3b57031202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 783320d2acdf7c09df5267f6e3e1ec506499ef9970f60ded4eae13205df4bedd 0.600000000000 1457454 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": 997036, "vin": [ { "gen": { "height": 997026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "783320d2acdf7c09df5267f6e3e1ec506499ef9970f60ded4eae13205df4bedd" } } ], "extra": [ 1, 239, 200, 121, 129, 206, 49, 140, 105, 43, 1, 191, 127, 93, 63, 209, 187, 158, 217, 29, 145, 5, 178, 130, 146, 200, 146, 170, 218, 59, 87, 3, 18, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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