Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ab51c4070bd87101ec60f205652ddb6e5ecd3a55b99c51c6ae1b40ddbd0a52d

Tx prefix hash: 0264446ff9924c60b8eac30be928a80e8198425eb07ae5c0fab599508162439b
Tx public key: a268d16fe3106acd03c6848140beffdf893bc8c23a1e1bd21d9c8da2596dab16
Timestamp: 1713684904 Timestamp [UCT]: 2024-04-21 07:35:04 Age [y:d:h:m:s]: 00:330:04:50:03
Block: 1005190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236079 RingCT/type: yes/0
Extra: 01a268d16fe3106acd03c6848140beffdf893bc8c23a1e1bd21d9c8da2596dab160211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f826ae065de8c76ce835fb5d077033527da2b34fce3ca3b261aecb5eb49b502 0.600000000000 1465774 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": 1005200, "vin": [ { "gen": { "height": 1005190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f826ae065de8c76ce835fb5d077033527da2b34fce3ca3b261aecb5eb49b502" } } ], "extra": [ 1, 162, 104, 209, 111, 227, 16, 106, 205, 3, 198, 132, 129, 64, 190, 255, 223, 137, 59, 200, 194, 58, 30, 27, 210, 29, 156, 141, 162, 89, 109, 171, 22, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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