Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c089aa71f9ca26c02b9465c3c151733a4336b65e31b3767ffc52ce936fdb08c

Tx prefix hash: faa1a413f28fe457df8412629d84cf339acf5df380090a0da942654474ea227d
Tx public key: 589c40dd52b12058119b668e4c7e1e6db45e3f5e926655d9b11422aa1034a710
Timestamp: 1737135513 Timestamp [UCT]: 2025-01-17 17:38:33 Age [y:d:h:m:s]: 00:151:08:22:58
Block: 1199464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107875 RingCT/type: yes/0
Extra: 01589c40dd52b12058119b668e4c7e1e6db45e3f5e926655d9b11422aa1034a710021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ba922a6b24df53e3536a6a25e78e6448d3389dd7b84a723b0ac02051ba60d43 0.600000000000 1686095 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": 1199474, "vin": [ { "gen": { "height": 1199464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ba922a6b24df53e3536a6a25e78e6448d3389dd7b84a723b0ac02051ba60d43" } } ], "extra": [ 1, 88, 156, 64, 221, 82, 177, 32, 88, 17, 155, 102, 142, 76, 126, 30, 109, 180, 94, 63, 94, 146, 102, 85, 217, 177, 20, 34, 170, 16, 52, 167, 16, 2, 17, 0, 0, 0, 2, 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