Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1762dcc3b1233779c50bed8c5818ec81694f054ccfcb92c5bd55c7b66cbb3dc

Tx prefix hash: 4b2afccc59934e13a7e57c44b3e82e1f589e9ab9c0eeeb55acbfa475ab67e1df
Tx public key: 575641e7e6a225270f1b7e08f6cf79565222b7676d8e7bf30031f700fb9c109e
Timestamp: 1736330747 Timestamp [UCT]: 2025-01-08 10:05:47 Age [y:d:h:m:s]: 00:165:09:57:23
Block: 1192808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117839 RingCT/type: yes/0
Extra: 01575641e7e6a225270f1b7e08f6cf79565222b7676d8e7bf30031f700fb9c109e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb560b072ea1c73ffbca09a066ec79b5a0fdd02e011de14a5644bf3768838505 0.600000000000 1679365 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": 1192818, "vin": [ { "gen": { "height": 1192808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb560b072ea1c73ffbca09a066ec79b5a0fdd02e011de14a5644bf3768838505" } } ], "extra": [ 1, 87, 86, 65, 231, 230, 162, 37, 39, 15, 27, 126, 8, 246, 207, 121, 86, 82, 34, 183, 103, 109, 142, 123, 243, 0, 49, 247, 0, 251, 156, 16, 158, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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