Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e4ca8bf414bacdf9b2082cf2dd64d2defd8c3391dac83363037b16b9eef36ca

Tx prefix hash: 9e2bcb27266245ab85f8ecdbc4467a9a7a86d0525c13e9fce966a3e62ed3f643
Tx public key: 299073ae0f2a8435e3792fa90de93bb474ab64a2c8acd1b3c74b9e15850cddda
Timestamp: 1761295377 Timestamp [UCT]: 2025-10-24 08:42:57 Age [y:d:h:m:s]: 00:071:04:10:45
Block: 1396810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50949 RingCT/type: yes/0
Extra: 01299073ae0f2a8435e3792fa90de93bb474ab64a2c8acd1b3c74b9e15850cddda021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4b2cf2843120aa21786dfce94c5f57401e1e2efc5cd503539568a904925611f 0.600000000000 1885097 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": 1396820, "vin": [ { "gen": { "height": 1396810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4b2cf2843120aa21786dfce94c5f57401e1e2efc5cd503539568a904925611f" } } ], "extra": [ 1, 41, 144, 115, 174, 15, 42, 132, 53, 227, 121, 47, 169, 13, 233, 59, 180, 116, 171, 100, 162, 200, 172, 209, 179, 199, 75, 158, 21, 133, 12, 221, 218, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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