Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25aa04e08b431ca84b0d37ad1a1fdde8c7cfef41a214ec265e8eb9795b87b68c

Tx prefix hash: 2836d87b06bee9263469eb1a0cbe3a904ea98eae478510eb9b0cf8bd0aef25a9
Tx public key: 8420cc9f3c8c8e72a78379d5c6e81976dd5e082b327069552afd82085dab82f9
Timestamp: 1766756058 Timestamp [UCT]: 2025-12-26 13:34:18 Age [y:d:h:m:s]: 00:011:05:58:32
Block: 1442048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8056 RingCT/type: yes/0
Extra: 018420cc9f3c8c8e72a78379d5c6e81976dd5e082b327069552afd82085dab82f902110000000dd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96a71c3d0447fe53df091a39fea84e4803c673325ace2e28d04039f880112b35 0.600000000000 1930947 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": 1442058, "vin": [ { "gen": { "height": 1442048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96a71c3d0447fe53df091a39fea84e4803c673325ace2e28d04039f880112b35" } } ], "extra": [ 1, 132, 32, 204, 159, 60, 140, 142, 114, 167, 131, 121, 213, 198, 232, 25, 118, 221, 94, 8, 43, 50, 112, 105, 85, 42, 253, 130, 8, 93, 171, 130, 249, 2, 17, 0, 0, 0, 13, 214, 225, 157, 124, 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