Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad7c248356729bb0bf16308eef457345116c1a2d0a1438624a3daeeb65544889

Tx prefix hash: f766522e692d076fde45f617c1e66d4f21c911a0affe00229afe165b6a32d4ed
Tx public key: d6b4dc653c5bc5c1b6089618f9e57a17ff37ab5a2291b028c2876fd69299cfea
Timestamp: 1748515658 Timestamp [UCT]: 2025-05-29 10:47:38 Age [y:d:h:m:s]: 00:165:14:27:15
Block: 1293433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116022 RingCT/type: yes/0
Extra: 01d6b4dc653c5bc5c1b6089618f9e57a17ff37ab5a2291b028c2876fd69299cfea021100000002c1263626000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a33332b0d67b8515b6f98599fc6a9613328d37893048dbc9d2defc02af2872b 0.600000000000 1780906 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": 1293443, "vin": [ { "gen": { "height": 1293433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a33332b0d67b8515b6f98599fc6a9613328d37893048dbc9d2defc02af2872b" } } ], "extra": [ 1, 214, 180, 220, 101, 60, 91, 197, 193, 182, 8, 150, 24, 249, 229, 122, 23, 255, 55, 171, 90, 34, 145, 176, 40, 194, 135, 111, 214, 146, 153, 207, 234, 2, 17, 0, 0, 0, 2, 193, 38, 54, 38, 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