Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6aa8eddd7191080ae5fbe656acf5dbb42fbf96c0eeb7508eea0ef2e5ddd9e215

Tx prefix hash: bf73f8554777f14bcb956f9ef153441710ea2c273228f0ff8aa5d992669c1056
Tx public key: d01b1c5c6dcf326fe57ce1e6ee36960ac2a1aa802a20131e8758c737523b8599
Timestamp: 1702955768 Timestamp [UCT]: 2023-12-19 03:16:08 Age [y:d:h:m:s]: 01:353:19:53:01
Block: 916256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511758 RingCT/type: yes/0
Extra: 01d01b1c5c6dcf326fe57ce1e6ee36960ac2a1aa802a20131e8758c737523b8599021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3694cdd716430c8a84608a22f129d8c439aca1a764227f203576e6209a1670b 0.600000000000 1373740 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": 916266, "vin": [ { "gen": { "height": 916256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3694cdd716430c8a84608a22f129d8c439aca1a764227f203576e6209a1670b" } } ], "extra": [ 1, 208, 27, 28, 92, 109, 207, 50, 111, 229, 124, 225, 230, 238, 54, 150, 10, 194, 161, 170, 128, 42, 32, 19, 30, 135, 88, 199, 55, 82, 59, 133, 153, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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