Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26b3591b7877324b337d9ce338e78200da44c5bc87fd2a7796d8fd865bd987f1

Tx prefix hash: 41c13845c159c7e1f46663b1d9c3818b8de9ffdd5af0951530ffb29c9f2a12b7
Tx public key: 057f0a2bcc48f6776dccd9e2c705c5bcf7040a03b279e9a871ff53f602faba34
Timestamp: 1669291020 Timestamp [UCT]: 2022-11-24 11:57:00 Age [y:d:h:m:s]: 02:137:22:55:34
Block: 638050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 620318 RingCT/type: yes/0
Extra: 01057f0a2bcc48f6776dccd9e2c705c5bcf7040a03b279e9a871ff53f602faba34021100000002e6d27f9c000000000000000000

1 output(s) for total of 4.719277192000 dcy

stealth address amount amount idx
00: 72eabe5c262e5ee11e05aea53f7a65adcf1a693afe3f912667e80983e64903c9 4.719277192000 1077643 of 0

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": 638060, "vin": [ { "gen": { "height": 638050 } } ], "vout": [ { "amount": 4719277192, "target": { "key": "72eabe5c262e5ee11e05aea53f7a65adcf1a693afe3f912667e80983e64903c9" } } ], "extra": [ 1, 5, 127, 10, 43, 204, 72, 246, 119, 109, 204, 217, 226, 199, 5, 197, 188, 247, 4, 10, 3, 178, 121, 233, 168, 113, 255, 83, 246, 2, 250, 186, 52, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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