Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbadc888b1098343e08f21fd6e7ce423190fb2ef14bf91f45e7e8637d9a18329

Tx prefix hash: 8e96874265b166654a76fb76ce2d2bc3df4e7d7ec6dd5a065b35304aae178c92
Tx public key: 618cfe2e3037faacfbb31c8932270ac714a44632d777dc3e75e1d520eca35b43
Timestamp: 1720498644 Timestamp [UCT]: 2024-07-09 04:17:24 Age [y:d:h:m:s]: 01:160:17:43:20
Block: 1061692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373443 RingCT/type: yes/0
Extra: 01618cfe2e3037faacfbb31c8932270ac714a44632d777dc3e75e1d520eca35b4302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e50a41d4a10a252d34352c37cb2f087e0908b2482f8a49bfb2347403b7ffe957 0.600000000000 1532187 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": 1061702, "vin": [ { "gen": { "height": 1061692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e50a41d4a10a252d34352c37cb2f087e0908b2482f8a49bfb2347403b7ffe957" } } ], "extra": [ 1, 97, 140, 254, 46, 48, 55, 250, 172, 251, 179, 28, 137, 50, 39, 10, 199, 20, 164, 70, 50, 215, 119, 220, 62, 117, 225, 213, 32, 236, 163, 91, 67, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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