Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8c22d21f839c44fff3fb33c8bb9aad1bce0aab561ca0b00c0f991943adb0ebb

Tx prefix hash: 2b2a8f9672f4f73892de67338f9d007a1b2995c802020eba90f2fd36aadc2cc1
Tx public key: 9487345f3ee17178201184aa5334675f1c8fb2cc7d84c51d49a60d69cd51f6a9
Timestamp: 1745272246 Timestamp [UCT]: 2025-04-21 21:50:46 Age [y:d:h:m:s]: 00:023:12:20:24
Block: 1266564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16822 RingCT/type: yes/0
Extra: 019487345f3ee17178201184aa5334675f1c8fb2cc7d84c51d49a60d69cd51f6a902110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f3c2649e27c323b1f10e9950e176ef5d179205e6c531b362e80b7d01e12f0a5 0.600000000000 1753785 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": 1266574, "vin": [ { "gen": { "height": 1266564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f3c2649e27c323b1f10e9950e176ef5d179205e6c531b362e80b7d01e12f0a5" } } ], "extra": [ 1, 148, 135, 52, 95, 62, 225, 113, 120, 32, 17, 132, 170, 83, 52, 103, 95, 28, 143, 178, 204, 125, 132, 197, 29, 73, 166, 13, 105, 205, 81, 246, 169, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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