Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f37e717417a1b3af6967f801c2830d2c31b1874b98b84bc6b23ec269066dfce

Tx prefix hash: 800e9186634240cccef3dfc14b272a2a2ff1eec81eced435abf812706e75138d
Tx public key: b2bfe1e5a7a7e5c4e9cf3e90d1baa8155a97db7f320e6772bcad43d7e16d3d64
Timestamp: 1698128906 Timestamp [UCT]: 2023-10-24 06:28:26 Age [y:d:h:m:s]: 02:014:04:16:38
Block: 876438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529705 RingCT/type: yes/0
Extra: 01b2bfe1e5a7a7e5c4e9cf3e90d1baa8155a97db7f320e6772bcad43d7e16d3d6402110000000e75e3f0e9000000000000000000

1 output(s) for total of 0.765591490000 dcy

stealth address amount amount idx
00: 017313e6cf645112826bf58e2ac8edc4a8ae08677d2dbbe90b9ec789a497be26 0.765591490000 1331762 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": 876448, "vin": [ { "gen": { "height": 876438 } } ], "vout": [ { "amount": 765591490, "target": { "key": "017313e6cf645112826bf58e2ac8edc4a8ae08677d2dbbe90b9ec789a497be26" } } ], "extra": [ 1, 178, 191, 225, 229, 167, 167, 229, 196, 233, 207, 62, 144, 209, 186, 168, 21, 90, 151, 219, 127, 50, 14, 103, 114, 188, 173, 67, 215, 225, 109, 61, 100, 2, 17, 0, 0, 0, 14, 117, 227, 240, 233, 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