Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05b9c51618a677e64d84cb4cfd1906881a4c8d59a227ba130b709f624b59651b

Tx prefix hash: 98e64e8352a280cad003e859c718e36882ee2ba1af0798fcb45dc907d5f333d0
Tx public key: 5d2be63a509e08ca17852d88396e3ae8e26ebad370076486eb200d7c6b70d98c
Timestamp: 1705663334 Timestamp [UCT]: 2024-01-19 11:22:14 Age [y:d:h:m:s]: 01:038:00:08:39
Block: 938667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288238 RingCT/type: yes/0
Extra: 015d2be63a509e08ca17852d88396e3ae8e26ebad370076486eb200d7c6b70d98c02110000000682025268000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cbf2bf23d38a3b6ca991e8dcf7332c0a345e0d82a4c16b8bb6b5c47fcd9a321 0.600000000000 1396739 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": 938677, "vin": [ { "gen": { "height": 938667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cbf2bf23d38a3b6ca991e8dcf7332c0a345e0d82a4c16b8bb6b5c47fcd9a321" } } ], "extra": [ 1, 93, 43, 230, 58, 80, 158, 8, 202, 23, 133, 45, 136, 57, 110, 58, 232, 226, 110, 186, 211, 112, 7, 100, 134, 235, 32, 13, 124, 107, 112, 217, 140, 2, 17, 0, 0, 0, 6, 130, 2, 82, 104, 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