Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5d0ed82fed03f14c3447f8d5722fa36c675e4f63b13e579724b74011765a619

Tx prefix hash: 5c057a3758ab29c421601e66a9d2ec12e9a017b0b68c86cb9e63f0d4535e105c
Tx public key: 56a89b27c8aeec49c7f8757f17ae20ef08b3af668c95b04225bac31631e5de09
Timestamp: 1733408401 Timestamp [UCT]: 2024-12-05 14:20:01 Age [y:d:h:m:s]: 00:344:17:43:30
Block: 1168619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243901 RingCT/type: yes/0
Extra: 0156a89b27c8aeec49c7f8757f17ae20ef08b3af668c95b04225bac31631e5de09021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e06463060b1bc31f4520f1bdd2bde5951874b96f2574ba62da36d3096b9b4f74 0.600000000000 1654330 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": 1168629, "vin": [ { "gen": { "height": 1168619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e06463060b1bc31f4520f1bdd2bde5951874b96f2574ba62da36d3096b9b4f74" } } ], "extra": [ 1, 86, 168, 155, 39, 200, 174, 236, 73, 199, 248, 117, 127, 23, 174, 32, 239, 8, 179, 175, 102, 140, 149, 176, 66, 37, 186, 195, 22, 49, 229, 222, 9, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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