Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35689da450a02a796122b6e70f5c4391e9721f465b20d952db37422d4114252f

Tx prefix hash: b1c72374c06a69929f728b90a789dddfef25b674926cc95ab730cc52503e35c9
Tx public key: 043b067c49dace378b1f5fb12b13eb34afe076d95630e0e2fa8b2659093dd438
Timestamp: 1676535435 Timestamp [UCT]: 2023-02-16 08:17:15 Age [y:d:h:m:s]: 02:110:01:52:35
Block: 698090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 600331 RingCT/type: yes/0
Extra: 01043b067c49dace378b1f5fb12b13eb34afe076d95630e0e2fa8b2659093dd43802110000000352542ceb000000000000000000

1 output(s) for total of 2.984956147000 dcy

stealth address amount amount idx
00: b8a4af0d0cf46fd30233ceb66e9c3496756b510b4da56a0aac0d418b8619c445 2.984956147000 1141361 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": 698100, "vin": [ { "gen": { "height": 698090 } } ], "vout": [ { "amount": 2984956147, "target": { "key": "b8a4af0d0cf46fd30233ceb66e9c3496756b510b4da56a0aac0d418b8619c445" } } ], "extra": [ 1, 4, 59, 6, 124, 73, 218, 206, 55, 139, 31, 95, 177, 43, 19, 235, 52, 175, 224, 118, 217, 86, 48, 224, 226, 250, 139, 38, 89, 9, 61, 212, 56, 2, 17, 0, 0, 0, 3, 82, 84, 44, 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