Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93329620d2001e3ae8bf0d9da35984882f16af04f6b9f51ade78e3855b8f9e41

Tx prefix hash: c63a4c8c718b4e0b91346e38b4c9cd942a093927a37840b6fe961bead6121567
Tx public key: cca33dc3dfd3de04a91b1e662c6e73a06ebeffc937f86a7f9089841bf3714def
Timestamp: 1721612442 Timestamp [UCT]: 2024-07-22 01:40:42 Age [y:d:h:m:s]: 00:240:09:10:08
Block: 1070911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171745 RingCT/type: yes/0
Extra: 01cca33dc3dfd3de04a91b1e662c6e73a06ebeffc937f86a7f9089841bf3714def021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 001b71aa900dad4d169fa771b7a7f6efed8e02ccd0dd682179af7675c29a0cae 0.600000000000 1542938 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": 1070921, "vin": [ { "gen": { "height": 1070911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "001b71aa900dad4d169fa771b7a7f6efed8e02ccd0dd682179af7675c29a0cae" } } ], "extra": [ 1, 204, 163, 61, 195, 223, 211, 222, 4, 169, 27, 30, 102, 44, 110, 115, 160, 110, 190, 255, 201, 55, 248, 106, 127, 144, 137, 132, 27, 243, 113, 77, 239, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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