Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cb5ff65eef3804c9359ca80951eb458a22bd5fedb7233a06740d14ef7c6ff09

Tx prefix hash: 279c6fe29225afde85970c693a537341af3d4f1756fb61259f02faa6b01b0922
Tx public key: c4684aa8f1df99f71f01ae9a4918b8abee674a8d694bcadafca48bfcf8fd6d85
Timestamp: 1757083581 Timestamp [UCT]: 2025-09-05 14:46:21 Age [y:d:h:m:s]: 00:119:21:04:49
Block: 1361973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85760 RingCT/type: yes/0
Extra: 01c4684aa8f1df99f71f01ae9a4918b8abee674a8d694bcadafca48bfcf8fd6d85021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d4c334fe31a502c504b83f8939fb25037de7651b42faafa5311f34573b65df7 0.600000000000 1849996 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": 1361983, "vin": [ { "gen": { "height": 1361973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d4c334fe31a502c504b83f8939fb25037de7651b42faafa5311f34573b65df7" } } ], "extra": [ 1, 196, 104, 74, 168, 241, 223, 153, 247, 31, 1, 174, 154, 73, 24, 184, 171, 238, 103, 74, 141, 105, 75, 202, 218, 252, 164, 139, 252, 248, 253, 109, 133, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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