Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ef506e62783a0bb8fb2f3ab3d2257986d138f278ec7376fc3786ad58ea561e4

Tx prefix hash: 64954690446afab3b422cd89b38776181538c9456e97e80bf3420ba61e2b79b4
Tx public key: 4a945d9c3236765dd2717ca9f8efeece1b7fb8e98abafbc18dedd913ff62cdd5
Timestamp: 1673805489 Timestamp [UCT]: 2023-01-15 17:58:09 Age [y:d:h:m:s]: 02:039:12:35:01
Block: 675436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549880 RingCT/type: yes/0
Extra: 014a945d9c3236765dd2717ca9f8efeece1b7fb8e98abafbc18dedd913ff62cdd50211000000018b7b6602000000000000000000

1 output(s) for total of 3.548134664000 dcy

stealth address amount amount idx
00: f2960a9e647caf3c611baf1c26814155540a0d3217c8d6dd8a2af7550f8f4d25 3.548134664000 1117111 of 0

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": 675446, "vin": [ { "gen": { "height": 675436 } } ], "vout": [ { "amount": 3548134664, "target": { "key": "f2960a9e647caf3c611baf1c26814155540a0d3217c8d6dd8a2af7550f8f4d25" } } ], "extra": [ 1, 74, 148, 93, 156, 50, 54, 118, 93, 210, 113, 124, 169, 248, 239, 238, 206, 27, 127, 184, 233, 138, 186, 251, 193, 141, 237, 217, 19, 255, 98, 205, 213, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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