Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c9c457de704e6bcb7deacc079fe3115c739d14797e5d2129d020e7dd6863893

Tx prefix hash: fede3d7a0ae4ce8252fac39ae3ee49761c6798c41765702199e86bf4ac5f8290
Tx public key: 574e4b57f40db6e7efb49c22f0a26d283d614eb52bf8ad536103efef1e33b890
Timestamp: 1712604498 Timestamp [UCT]: 2024-04-08 19:28:18 Age [y:d:h:m:s]: 01:029:06:38:52
Block: 996214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281922 RingCT/type: yes/0
Extra: 01574e4b57f40db6e7efb49c22f0a26d283d614eb52bf8ad536103efef1e33b89002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cde723891db093001db1a56cc4ddddb00b4f3b0f0f40d041f7bcc6f1c69fe6e9 0.600000000000 1456630 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": 996224, "vin": [ { "gen": { "height": 996214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cde723891db093001db1a56cc4ddddb00b4f3b0f0f40d041f7bcc6f1c69fe6e9" } } ], "extra": [ 1, 87, 78, 75, 87, 244, 13, 182, 231, 239, 180, 156, 34, 240, 162, 109, 40, 61, 97, 78, 181, 43, 248, 173, 83, 97, 3, 239, 239, 30, 51, 184, 144, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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