Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b98296abf1a03f26c020cc47b80c9e96b7872be54f91974bd3ee5899d998e369

Tx prefix hash: 934375ad4951f694a1a9b3cb0b574a7be18c30f39265cfa7c3c6654fe8e1694f
Tx public key: 9fa7ecb4499250f6a3296ac8280b87caeffb4f882403989c5d4b6a08f1a9bb3d
Timestamp: 1702969166 Timestamp [UCT]: 2023-12-19 06:59:26 Age [y:d:h:m:s]: 01:135:11:29:09
Block: 916377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357954 RingCT/type: yes/0
Extra: 019fa7ecb4499250f6a3296ac8280b87caeffb4f882403989c5d4b6a08f1a9bb3d02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c371bf5b79dbed67ad4586119823d9579c4db93b56f17a0f9548be44cf3b2887 0.600000000000 1373881 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": 916387, "vin": [ { "gen": { "height": 916377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c371bf5b79dbed67ad4586119823d9579c4db93b56f17a0f9548be44cf3b2887" } } ], "extra": [ 1, 159, 167, 236, 180, 73, 146, 80, 246, 163, 41, 106, 200, 40, 11, 135, 202, 239, 251, 79, 136, 36, 3, 152, 156, 93, 75, 106, 8, 241, 169, 187, 61, 2, 17, 0, 0, 0, 7, 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