Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08a3054d16ae77265567b1752402b3ef5affea05c7b5bad35fd7c7c5ac53d0d0

Tx prefix hash: a5a74d2165bed3f2d271d43581c5fd69214f3cec7ecb149c26c2695f7693c396
Tx public key: ae64af8f0e0e275ea2495b523dfa06d8efe437de104742ab396004899f9cdb5f
Timestamp: 1736812808 Timestamp [UCT]: 2025-01-14 00:00:08 Age [y:d:h:m:s]: 00:059:12:19:40
Block: 1196798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42329 RingCT/type: yes/0
Extra: 01ae64af8f0e0e275ea2495b523dfa06d8efe437de104742ab396004899f9cdb5f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74b3c81766d87b689252d65568850f0533801ef80955d0ea3e242c55355b6b07 0.600000000000 1683401 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": 1196808, "vin": [ { "gen": { "height": 1196798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74b3c81766d87b689252d65568850f0533801ef80955d0ea3e242c55355b6b07" } } ], "extra": [ 1, 174, 100, 175, 143, 14, 14, 39, 94, 162, 73, 91, 82, 61, 250, 6, 216, 239, 228, 55, 222, 16, 71, 66, 171, 57, 96, 4, 137, 159, 156, 219, 95, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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