Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f38da2c936a60ec677a5252d4bf837a127090788d9113b058d665809b0df7436

Tx prefix hash: e9a9b7810919e284565569c0df02ceb68d88e4aa9ab182be3dcfa57fb911605e
Tx public key: 6abf3c1282a4f49696c2e8d7a2400a0ed8632e1f30e930aed9b7b3e6e30b3dbb
Timestamp: 1737733858 Timestamp [UCT]: 2025-01-24 15:50:58 Age [y:d:h:m:s]: 00:145:17:08:59
Block: 1204375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103868 RingCT/type: yes/0
Extra: 016abf3c1282a4f49696c2e8d7a2400a0ed8632e1f30e930aed9b7b3e6e30b3dbb0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b7eed0db21009076f206d3d65aa26c0853029a4b838e466a6f436627144b039 0.600000000000 1691060 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": 1204385, "vin": [ { "gen": { "height": 1204375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b7eed0db21009076f206d3d65aa26c0853029a4b838e466a6f436627144b039" } } ], "extra": [ 1, 106, 191, 60, 18, 130, 164, 244, 150, 150, 194, 232, 215, 162, 64, 10, 14, 216, 99, 46, 31, 48, 233, 48, 174, 217, 183, 179, 230, 227, 11, 61, 187, 2, 17, 0, 0, 0, 9, 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