Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ba8e441a29d5169fa08602a71e18ae74626238cabe7b555018667f69b9dbd7c

Tx prefix hash: 3ca24a71ed6e3f853d9b7d58e41863136e5404a03dd789868c40d6d975f9dcd9
Tx public key: 155685b1212d5d0094f0ed1fadd7e9d504c1cafca625f7afbff14ff771cb726a
Timestamp: 1715055594 Timestamp [UCT]: 2024-05-07 04:19:54 Age [y:d:h:m:s]: 00:239:11:13:21
Block: 1016571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171394 RingCT/type: yes/0
Extra: 01155685b1212d5d0094f0ed1fadd7e9d504c1cafca625f7afbff14ff771cb726a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05cf9d0f88b804276f358b1bb7108cbeb18d7fb21035378b69833b73824c576a 0.600000000000 1480192 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": 1016581, "vin": [ { "gen": { "height": 1016571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05cf9d0f88b804276f358b1bb7108cbeb18d7fb21035378b69833b73824c576a" } } ], "extra": [ 1, 21, 86, 133, 177, 33, 45, 93, 0, 148, 240, 237, 31, 173, 215, 233, 213, 4, 193, 202, 252, 166, 37, 247, 175, 191, 241, 79, 247, 113, 203, 114, 106, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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