Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33f6c25eb9f28d05ad7348f0761d5c68866ed726c6decd2edf4c4d7733f65b1b

Tx prefix hash: f8efc150a88944cab637a1c2c5bbb1735f3c5fa9a19cf3f904bf91e957bd9431
Tx public key: 260e84c87f14ae8c377531a59fd9b4df466c4f6981681026252428948fd731d3
Timestamp: 1723525232 Timestamp [UCT]: 2024-08-13 05:00:32 Age [y:d:h:m:s]: 00:238:00:34:29
Block: 1086780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169980 RingCT/type: yes/0
Extra: 01260e84c87f14ae8c377531a59fd9b4df466c4f6981681026252428948fd731d3021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d1b47b63627543ed371b866c22d5edcb3f22316ae607f4093ffbf1b98762286 0.600000000000 1561379 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": 1086790, "vin": [ { "gen": { "height": 1086780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d1b47b63627543ed371b866c22d5edcb3f22316ae607f4093ffbf1b98762286" } } ], "extra": [ 1, 38, 14, 132, 200, 127, 20, 174, 140, 55, 117, 49, 165, 159, 217, 180, 223, 70, 108, 79, 105, 129, 104, 16, 38, 37, 36, 40, 148, 143, 215, 49, 211, 2, 17, 0, 0, 0, 4, 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