Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10a982e76d6ab028e714c6b19587c735818e9bb68bb880f5ced61e2e6bfecc7f

Tx prefix hash: c791b96ab07d1775bd9e9665a92877a7e563b8b6be1d78bd3523e615afddf797
Tx public key: 274ecfbd20dcfc3934d6c760f070688ff13b56ef8d8ec2bdc0f99e34f5e8a1b3
Timestamp: 1751614847 Timestamp [UCT]: 2025-07-04 07:40:47 Age [y:d:h:m:s]: 00:134:17:06:09
Block: 1318479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94547 RingCT/type: yes/0
Extra: 01274ecfbd20dcfc3934d6c760f070688ff13b56ef8d8ec2bdc0f99e34f5e8a1b302110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b08035ce6bbe3e8dd8c3d0c6438bf4797c328082a390ad51fa1cc3854906346 0.600000000000 1806160 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": 1318489, "vin": [ { "gen": { "height": 1318479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b08035ce6bbe3e8dd8c3d0c6438bf4797c328082a390ad51fa1cc3854906346" } } ], "extra": [ 1, 39, 78, 207, 189, 32, 220, 252, 57, 52, 214, 199, 96, 240, 112, 104, 143, 241, 59, 86, 239, 141, 142, 194, 189, 192, 249, 158, 52, 245, 232, 161, 179, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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