Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8eb0937f6fc1e970fe91df6f3d663ff6761221d93743fc84e31f55cd2ecd692

Tx prefix hash: d5dedcf91896ed86a49f46631c29ee4076be564ede09b2e58f9333f96741c087
Tx public key: c9574cfe53e9232bbb44afc313fe04c7e3ec6f59f1b9191f6d67c9f2340277f0
Timestamp: 1712053516 Timestamp [UCT]: 2024-04-02 10:25:16 Age [y:d:h:m:s]: 01:013:13:16:00
Block: 991647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270679 RingCT/type: yes/0
Extra: 01c9574cfe53e9232bbb44afc313fe04c7e3ec6f59f1b9191f6d67c9f2340277f00211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 228f663475155d77ea7039a93ca7c0f639716c0654ad0fad015cae0b4e8fb8fc 0.600000000000 1451983 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": 991657, "vin": [ { "gen": { "height": 991647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "228f663475155d77ea7039a93ca7c0f639716c0654ad0fad015cae0b4e8fb8fc" } } ], "extra": [ 1, 201, 87, 76, 254, 83, 233, 35, 43, 187, 68, 175, 195, 19, 254, 4, 199, 227, 236, 111, 89, 241, 185, 25, 31, 109, 103, 201, 242, 52, 2, 119, 240, 2, 17, 0, 0, 0, 2, 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