Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e0c3e48e0b3a9e553111b1f9a611142c58cfc4e96f5d59a35dd335adce7e4b2

Tx prefix hash: a9d20bb66b87040f3f6d1888e3ad9771ab6bd3a7d17b920a0d5468bf6a203522
Tx public key: 0d8d2c12cd88b5e5b17ba4b57bed2f47015ed4f2a56bc3f5beb133486c38c54a
Timestamp: 1730960042 Timestamp [UCT]: 2024-11-07 06:14:02 Age [y:d:h:m:s]: 00:076:10:40:12
Block: 1148335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54642 RingCT/type: yes/0
Extra: 010d8d2c12cd88b5e5b17ba4b57bed2f47015ed4f2a56bc3f5beb133486c38c54a02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3d8062d10efba56f0254a7cd595303aafe0d9ee0eec5e72710e4988520c033f 0.600000000000 1633152 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": 1148345, "vin": [ { "gen": { "height": 1148335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3d8062d10efba56f0254a7cd595303aafe0d9ee0eec5e72710e4988520c033f" } } ], "extra": [ 1, 13, 141, 44, 18, 205, 136, 181, 229, 177, 123, 164, 181, 123, 237, 47, 71, 1, 94, 212, 242, 165, 107, 195, 245, 190, 177, 51, 72, 108, 56, 197, 74, 2, 17, 0, 0, 0, 10, 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