Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f4fddc3369a2e684d24c860f76580c4a2edefbe77a05818411fccb5e1c3c4fd

Tx prefix hash: 3d17a7ccb7386460cad14a675a5e89eb778bb21e067fcf5d5e469201ebf9918e
Tx public key: a580a10a6baaccf1eca1d114343844bb0d5afdb901a809bcd3f00ebe46d58202
Timestamp: 1698336852 Timestamp [UCT]: 2023-10-26 16:14:12 Age [y:d:h:m:s]: 01:192:22:44:14
Block: 878179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398914 RingCT/type: yes/0
Extra: 01a580a10a6baaccf1eca1d114343844bb0d5afdb901a809bcd3f00ebe46d58202021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.755499511000 dcy

stealth address amount amount idx
00: e71f7a5dcae1388419deb1e3aa7316c754841c4f42bbcbc4a2732d3897aad138 0.755499511000 1333601 of 0

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": 878189, "vin": [ { "gen": { "height": 878179 } } ], "vout": [ { "amount": 755499511, "target": { "key": "e71f7a5dcae1388419deb1e3aa7316c754841c4f42bbcbc4a2732d3897aad138" } } ], "extra": [ 1, 165, 128, 161, 10, 107, 170, 204, 241, 236, 161, 209, 20, 52, 56, 68, 187, 13, 90, 253, 185, 1, 168, 9, 188, 211, 240, 14, 190, 70, 213, 130, 2, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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