Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0c99bc473283648d3ae24d04894f2e150efaf444be901fbc7a9940191b59e4

Tx prefix hash: f0e44a1fe706cb9fb8f9b3519166d80281a1ab392087d74180eec9ad075a2eb3
Tx public key: 2006af0f09d604375fc4d1e94ddfdd3d50aa56ebd3f5e0cad584fc825f332059
Timestamp: 1730561299 Timestamp [UCT]: 2024-11-02 15:28:19 Age [y:d:h:m:s]: 00:158:17:00:32
Block: 1145031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113264 RingCT/type: yes/0
Extra: 012006af0f09d604375fc4d1e94ddfdd3d50aa56ebd3f5e0cad584fc825f3320590211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a02de00b0ec7f7e266f1472cfa4733d98a6a79df323741c82fc6a89e1919601 0.600000000000 1629392 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": 1145041, "vin": [ { "gen": { "height": 1145031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a02de00b0ec7f7e266f1472cfa4733d98a6a79df323741c82fc6a89e1919601" } } ], "extra": [ 1, 32, 6, 175, 15, 9, 214, 4, 55, 95, 196, 209, 233, 77, 223, 221, 61, 80, 170, 86, 235, 211, 245, 224, 202, 213, 132, 252, 130, 95, 51, 32, 89, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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