Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0841c5c64c11045342363a2523590eed85a57b87df7c8cde195a57c7367a65a

Tx prefix hash: c0be1c36a878a2859adc7596c234e61e05bbb17125674e2e527528a7a535f0de
Tx public key: 11613207bf5d0b42c28763225ebfb847d9729bea580667ccc0ce9bc7d8625e4b
Timestamp: 1702216687 Timestamp [UCT]: 2023-12-10 13:58:07 Age [y:d:h:m:s]: 01:134:10:50:00
Block: 910117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357243 RingCT/type: yes/0
Extra: 0111613207bf5d0b42c28763225ebfb847d9729bea580667ccc0ce9bc7d8625e4b02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73d18030234ea14cf3de3c68354b4c5b4cb2e8a4f0971ffd3e38cf714ebe79d9 0.600000000000 1367262 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": 910127, "vin": [ { "gen": { "height": 910117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73d18030234ea14cf3de3c68354b4c5b4cb2e8a4f0971ffd3e38cf714ebe79d9" } } ], "extra": [ 1, 17, 97, 50, 7, 191, 93, 11, 66, 194, 135, 99, 34, 94, 191, 184, 71, 217, 114, 155, 234, 88, 6, 103, 204, 192, 206, 155, 199, 216, 98, 94, 75, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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