Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6ae066f5ac00b2cf57758337bcb5d2f1016724c358dfba179a6010d2bdd876f

Tx prefix hash: bcd3b8621d637a0f64f5dc6802ea324002aa0307670ea5638dce48b949650c69
Tx public key: 689fd6ba5d1b92b722aba61466558083f5c77213db4a01ae4ca5c14513e2d92a
Timestamp: 1728851818 Timestamp [UCT]: 2024-10-13 20:36:58 Age [y:d:h:m:s]: 00:177:20:47:02
Block: 1130941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126903 RingCT/type: yes/0
Extra: 01689fd6ba5d1b92b722aba61466558083f5c77213db4a01ae4ca5c14513e2d92a021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c468ca526fb0af2bd8410a41c56ff98d0be9e44d13a24f02aa321478cbb3fc3e 0.600000000000 1613822 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": 1130951, "vin": [ { "gen": { "height": 1130941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c468ca526fb0af2bd8410a41c56ff98d0be9e44d13a24f02aa321478cbb3fc3e" } } ], "extra": [ 1, 104, 159, 214, 186, 93, 27, 146, 183, 34, 171, 166, 20, 102, 85, 128, 131, 245, 199, 114, 19, 219, 74, 1, 174, 76, 165, 193, 69, 19, 226, 217, 42, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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