Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c199c7037c69ed7803c975a661c298dd96df65248abf353f9b01b1791c657d98

Tx prefix hash: 8edbfdc7d7bf691da2698f793fcfc4b33ee6fda4e3908c3a60bfe8e041c12d95
Tx public key: 2650ae0ad1ec000b206cdc491a1eb5471a56b46f030adbdd31e9981f92395c4a
Timestamp: 1750392024 Timestamp [UCT]: 2025-06-20 04:00:24 Age [y:d:h:m:s]: 00:148:22:27:46
Block: 1308812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104267 RingCT/type: yes/0
Extra: 012650ae0ad1ec000b206cdc491a1eb5471a56b46f030adbdd31e9981f92395c4a021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad0a89ea44a848db3c9a191f7c9455b3c610573a6d826b1a598be94bbc4b8f87 0.600000000000 1796427 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": 1308822, "vin": [ { "gen": { "height": 1308812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad0a89ea44a848db3c9a191f7c9455b3c610573a6d826b1a598be94bbc4b8f87" } } ], "extra": [ 1, 38, 80, 174, 10, 209, 236, 0, 11, 32, 108, 220, 73, 26, 30, 181, 71, 26, 86, 180, 111, 3, 10, 219, 221, 49, 233, 152, 31, 146, 57, 92, 74, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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