Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 421bdd476b39ac28fd738840e3c6e6057578c837812269a6a039eab1962cb58e

Tx prefix hash: c4b76fdaaf1849e89eb30fb9c84096e75f7a5212d148ad98667bd00dab9be1af
Tx public key: 2387c332a131874dae4a5257f84cdd06c068fd6437178b34deaf3b44a7d57f4d
Timestamp: 1724257513 Timestamp [UCT]: 2024-08-21 16:25:13 Age [y:d:h:m:s]: 00:142:04:38:00
Block: 1092866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101704 RingCT/type: yes/0
Extra: 012387c332a131874dae4a5257f84cdd06c068fd6437178b34deaf3b44a7d57f4d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c38bc94e21628a93c9f35b1572194a5da8db1e0c88ea2f25de15ba47bc2d844e 0.600000000000 1567697 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": 1092876, "vin": [ { "gen": { "height": 1092866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c38bc94e21628a93c9f35b1572194a5da8db1e0c88ea2f25de15ba47bc2d844e" } } ], "extra": [ 1, 35, 135, 195, 50, 161, 49, 135, 77, 174, 74, 82, 87, 248, 76, 221, 6, 192, 104, 253, 100, 55, 23, 139, 52, 222, 175, 59, 68, 167, 213, 127, 77, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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