Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d49574a7708499225716a9f571e46ba3f212d68bf129da57e143c2634e0eb250

Tx prefix hash: bb04c3646e823cd2997f7fcb7ae813c4b3f6fcf006d05c61e9c07e3cbc9da0c2
Tx public key: 63a6e85f9efc44d4f46e5633fda3d3cf64f56136a22d32ce0175cbea2e201d3d
Timestamp: 1727417404 Timestamp [UCT]: 2024-09-27 06:10:04 Age [y:d:h:m:s]: 01:043:07:32:06
Block: 1119059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289343 RingCT/type: yes/0
Extra: 0163a6e85f9efc44d4f46e5633fda3d3cf64f56136a22d32ce0175cbea2e201d3d02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7575993000edbb3a84d108936427357561bc3b01bfedd1b1b14cc89743dd183 0.600000000000 1600474 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": 1119069, "vin": [ { "gen": { "height": 1119059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7575993000edbb3a84d108936427357561bc3b01bfedd1b1b14cc89743dd183" } } ], "extra": [ 1, 99, 166, 232, 95, 158, 252, 68, 212, 244, 110, 86, 51, 253, 163, 211, 207, 100, 245, 97, 54, 162, 45, 50, 206, 1, 117, 203, 234, 46, 32, 29, 61, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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