Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81c91354c2fe4b1d4c29287abb1b10258ab281d08b14cc2ba210422d8a57b550

Tx prefix hash: 47f5ad419a78c2bf9ae1b43597efbd6703b166a987835ba5645a391fd39502d1
Tx public key: 545ae9a96f3e3af5ed405f115c0cb1318395fc04cb76d39f83b5133c1e93cbc1
Timestamp: 1762039218 Timestamp [UCT]: 2025-11-01 23:20:18 Age [y:d:h:m:s]: 00:006:12:02:06
Block: 1402967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4641 RingCT/type: yes/0
Extra: 01545ae9a96f3e3af5ed405f115c0cb1318395fc04cb76d39f83b5133c1e93cbc1021100000005df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3fc3ea0b46db75167c40cd09cd2666d5766e8b10b6097ac2be1180391ac70c3 0.600000000000 1891294 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": 1402977, "vin": [ { "gen": { "height": 1402967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3fc3ea0b46db75167c40cd09cd2666d5766e8b10b6097ac2be1180391ac70c3" } } ], "extra": [ 1, 84, 90, 233, 169, 111, 62, 58, 245, 237, 64, 95, 17, 92, 12, 177, 49, 131, 149, 252, 4, 203, 118, 211, 159, 131, 181, 19, 60, 30, 147, 203, 193, 2, 17, 0, 0, 0, 5, 223, 90, 36, 122, 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