Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 297b6926ee454b400d5c24dfd33d58071db6b2c582e6e496631a86dad59d2d66

Tx prefix hash: 8503f2e2e14548d037febdc2730d51ed6b5a52464cffec4a7bb2942171b9b815
Tx public key: 39f9065bd5efc6750d53df8737aa615c8ad123cabccb1692509e270e85184423
Timestamp: 1709749297 Timestamp [UCT]: 2024-03-06 18:21:37 Age [y:d:h:m:s]: 01:078:22:59:09
Block: 972584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317457 RingCT/type: yes/0
Extra: 0139f9065bd5efc6750d53df8737aa615c8ad123cabccb1692509e270e8518442302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cc4755f90fbdddb181b620dd4b49f563b9de4fde6e00cc25b3f2f95d16f8f1d 0.600000000000 1432499 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": 972594, "vin": [ { "gen": { "height": 972584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cc4755f90fbdddb181b620dd4b49f563b9de4fde6e00cc25b3f2f95d16f8f1d" } } ], "extra": [ 1, 57, 249, 6, 91, 213, 239, 198, 117, 13, 83, 223, 135, 55, 170, 97, 92, 138, 209, 35, 202, 188, 203, 22, 146, 80, 158, 39, 14, 133, 24, 68, 35, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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