Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a240785a5d73fd1dd5208180e4e22277f1c4bb316037afb7e92dd1230d69987

Tx prefix hash: c5401eac05518a1c0516d52eca8c296185496ccad515527fc93dfa6e025b2490
Tx public key: c53b3e862c612a7cf52f30ef5dd87ea6f9a1fd476c50d6790e7e5cfd6e68fe4a
Timestamp: 1639176525 Timestamp [UCT]: 2021-12-10 22:48:45 Age [y:d:h:m:s]: 03:046:02:09:01
Block: 392784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 811877 RingCT/type: yes/0
Extra: 01c53b3e862c612a7cf52f30ef5dd87ea6f9a1fd476c50d6790e7e5cfd6e68fe4a021100000015e9564d6f000000000000000000

1 output(s) for total of 30.658006898000 dcy

stealth address amount amount idx
00: c5eb6bb79cc7ee173385c5b4fbd5f5198308bdf291190a11bfd81ae2f0a55e54 30.658006898000 789787 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": 392794, "vin": [ { "gen": { "height": 392784 } } ], "vout": [ { "amount": 30658006898, "target": { "key": "c5eb6bb79cc7ee173385c5b4fbd5f5198308bdf291190a11bfd81ae2f0a55e54" } } ], "extra": [ 1, 197, 59, 62, 134, 44, 97, 42, 124, 245, 47, 48, 239, 93, 216, 126, 166, 249, 161, 253, 71, 108, 80, 214, 121, 14, 126, 92, 253, 110, 104, 254, 74, 2, 17, 0, 0, 0, 21, 233, 86, 77, 111, 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