Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 644116e8c041b25b5f0388152819f253a24b19520c1d846c12e13a7e1860b140

Tx prefix hash: 4e5eeee9e59458070c68438f1387b7b88c42b33db80ab1e385062660d92fb4d8
Tx public key: 70bfcb6c493b2ded42bede1f0cb20bc955a4d06d71ad50416c9903e354f5e4d0
Timestamp: 1760389143 Timestamp [UCT]: 2025-10-13 20:59:03 Age [y:d:h:m:s]: 00:037:08:26:21
Block: 1389301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26730 RingCT/type: yes/0
Extra: 0170bfcb6c493b2ded42bede1f0cb20bc955a4d06d71ad50416c9903e354f5e4d00211000000058368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83e5a7347cfb86eeeb11f4a4efabb601e6d0387d126942e14cfbe7556ad99caf 0.600000000000 1877530 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": 1389311, "vin": [ { "gen": { "height": 1389301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83e5a7347cfb86eeeb11f4a4efabb601e6d0387d126942e14cfbe7556ad99caf" } } ], "extra": [ 1, 112, 191, 203, 108, 73, 59, 45, 237, 66, 190, 222, 31, 12, 178, 11, 201, 85, 164, 208, 109, 113, 173, 80, 65, 108, 153, 3, 227, 84, 245, 228, 208, 2, 17, 0, 0, 0, 5, 131, 104, 38, 109, 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