Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6502c1714b85e782d743349f8a42e77d00f3d5071f2bb1773de4d9209899aaa3

Tx prefix hash: 06543b0341ccf91f0c405c407fe4ba88f2354b1473af94a010dec9a79be08245
Tx public key: 772ee23ba41e10ba2fdd9fc00f290af61c7cc7b1c5960f7fbe2f34ec8e4f7d3a
Timestamp: 1706222417 Timestamp [UCT]: 2024-01-25 22:40:17 Age [y:d:h:m:s]: 01:031:00:00:34
Block: 943307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283212 RingCT/type: yes/0
Extra: 01772ee23ba41e10ba2fdd9fc00f290af61c7cc7b1c5960f7fbe2f34ec8e4f7d3a02110000000f52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ba17c0d5dfa3b941603ad4715da74d42106e19e62d334393f8a2cc075228e0b 0.600000000000 1401513 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": 943317, "vin": [ { "gen": { "height": 943307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ba17c0d5dfa3b941603ad4715da74d42106e19e62d334393f8a2cc075228e0b" } } ], "extra": [ 1, 119, 46, 226, 59, 164, 30, 16, 186, 47, 221, 159, 192, 15, 41, 10, 246, 28, 124, 199, 177, 197, 150, 15, 127, 190, 47, 52, 236, 142, 79, 125, 58, 2, 17, 0, 0, 0, 15, 82, 212, 126, 148, 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