Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6a9159f3095be85c57834b54af4bccc467dc09e344edd0c987b9c71e849b84c

Tx prefix hash: 9d0120257638fdba57ce146b09792f2067cc5e1ecd2d7e63a2a9bf339f1ecab8
Tx public key: 068b82bb1b6203c98e59d32bf3043166bbde8e846fb085f068b47e8249739d88
Timestamp: 1705765016 Timestamp [UCT]: 2024-01-20 15:36:56 Age [y:d:h:m:s]: 01:292:16:00:49
Block: 939514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467988 RingCT/type: yes/0
Extra: 01068b82bb1b6203c98e59d32bf3043166bbde8e846fb085f068b47e8249739d8802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 892df85efc51510d68f6b1e773df6dc6d42762d14dd8f079cfb1e4dc1c036dfb 0.600000000000 1397622 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": 939524, "vin": [ { "gen": { "height": 939514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "892df85efc51510d68f6b1e773df6dc6d42762d14dd8f079cfb1e4dc1c036dfb" } } ], "extra": [ 1, 6, 139, 130, 187, 27, 98, 3, 201, 142, 89, 211, 43, 243, 4, 49, 102, 187, 222, 142, 132, 111, 176, 133, 240, 104, 180, 126, 130, 73, 115, 157, 136, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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