Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff2e3126aba7af95c0fa74c0d6a4661d9ad36010ee868f3d557191853b83cf01

Tx prefix hash: f2d201a4e44aa926805254ad2e77e5121f67dcdb360aea54f21694b4ba4da5f6
Tx public key: d8ed78eb99aa6f9cf3b08ebea92605b3b1ab650b55b89fd42df39da4e04513f7
Timestamp: 1750624386 Timestamp [UCT]: 2025-06-22 20:33:06 Age [y:d:h:m:s]: 00:148:11:02:33
Block: 1310672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103987 RingCT/type: yes/0
Extra: 01d8ed78eb99aa6f9cf3b08ebea92605b3b1ab650b55b89fd42df39da4e04513f7021100000009bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 494b59bac33e2897d174dd3e2e29b11f72bb492d8250a5226ecb15d237b20332 0.600000000000 1798293 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": 1310682, "vin": [ { "gen": { "height": 1310672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "494b59bac33e2897d174dd3e2e29b11f72bb492d8250a5226ecb15d237b20332" } } ], "extra": [ 1, 216, 237, 120, 235, 153, 170, 111, 156, 243, 176, 142, 190, 169, 38, 5, 179, 177, 171, 101, 11, 85, 184, 159, 212, 45, 243, 157, 164, 224, 69, 19, 247, 2, 17, 0, 0, 0, 9, 191, 81, 178, 162, 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