Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50b11f91fcb0c1007d9b0a63eb2d81b89bcc031dbfc797846d78ca0838bb26a0

Tx prefix hash: 746d5b5467c05ccc14b940937f7e6daa0405d543f00704d46fe134f40e166a63
Tx public key: 785b297fd2d3cccb5706cd92f8cd4caa9d342fff7c17f06f7cde8db07477ca20
Timestamp: 1705353863 Timestamp [UCT]: 2024-01-15 21:24:23 Age [y:d:h:m:s]: 01:098:14:41:00
Block: 936115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331590 RingCT/type: yes/0
Extra: 01785b297fd2d3cccb5706cd92f8cd4caa9d342fff7c17f06f7cde8db07477ca200211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ebc59296212bc9afd126d067c76be35f7c0d82dbd7c1e335772dc98cef2ff32 0.600000000000 1394137 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": 936125, "vin": [ { "gen": { "height": 936115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ebc59296212bc9afd126d067c76be35f7c0d82dbd7c1e335772dc98cef2ff32" } } ], "extra": [ 1, 120, 91, 41, 127, 210, 211, 204, 203, 87, 6, 205, 146, 248, 205, 76, 170, 157, 52, 47, 255, 124, 23, 240, 111, 124, 222, 141, 176, 116, 119, 202, 32, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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