Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82984fe55f7a7afa2a9043869ad2ba219fff21b11d3f1a85c4c91c907564faab

Tx prefix hash: f9755ff014b5b55fb820fa3b5ba886818e12aae72b2d0b19565f3e3fe899d71c
Tx public key: a6ce10f5d2203626775b3d49276b54629cdded77c14e41b425259069bb1e4dc0
Timestamp: 1740169798 Timestamp [UCT]: 2025-02-21 20:29:58 Age [y:d:h:m:s]: 00:228:08:36:20
Block: 1224309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160909 RingCT/type: yes/0
Extra: 01a6ce10f5d2203626775b3d49276b54629cdded77c14e41b425259069bb1e4dc0021100000010007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc5de4cc133ab98ae2453823c2fd0c0540df7a59b9567be1c77cbe48cafd11a4 0.600000000000 1711168 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": 1224319, "vin": [ { "gen": { "height": 1224309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc5de4cc133ab98ae2453823c2fd0c0540df7a59b9567be1c77cbe48cafd11a4" } } ], "extra": [ 1, 166, 206, 16, 245, 210, 32, 54, 38, 119, 91, 61, 73, 39, 107, 84, 98, 156, 221, 237, 119, 193, 78, 65, 180, 37, 37, 144, 105, 187, 30, 77, 192, 2, 17, 0, 0, 0, 16, 0, 127, 151, 138, 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