Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f8efbee8f096dcd2a9613c595d434595c18f4cacb0a3499450f03d182b1c0ab

Tx prefix hash: 3118597e72ec5b89f4d4ec40afe7bdea13414f9eae9bca56e7c06eae45d275f9
Tx public key: ca7378b3d0395284ac0fe150df7a72c558d116fd086f205025e3a16c23bbdb0f
Timestamp: 1736136160 Timestamp [UCT]: 2025-01-06 04:02:40 Age [y:d:h:m:s]: 00:088:00:37:37
Block: 1191206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62681 RingCT/type: yes/0
Extra: 01ca7378b3d0395284ac0fe150df7a72c558d116fd086f205025e3a16c23bbdb0f0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fee1a304fb27d3e7a087376b25187f58aa98a6e17bcd6b76e0c05ce2cae36e53 0.600000000000 1677729 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": 1191216, "vin": [ { "gen": { "height": 1191206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fee1a304fb27d3e7a087376b25187f58aa98a6e17bcd6b76e0c05ce2cae36e53" } } ], "extra": [ 1, 202, 115, 120, 179, 208, 57, 82, 132, 172, 15, 225, 80, 223, 122, 114, 197, 88, 209, 22, 253, 8, 111, 32, 80, 37, 227, 161, 108, 35, 187, 219, 15, 2, 17, 0, 0, 0, 7, 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