Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47fa8beca68910f17e071d3d0a6d91b3a8e4b6bf26675bf0017470798f05b89e

Tx prefix hash: 3368551bd087003016dcb409512b63292fdb76f1ab78490fc88e501df78c9cda
Tx public key: f7b6600f109feb7bf6c0e2ec67a1ee23042dcefe9932cab5af01a656bfb4ca8c
Timestamp: 1723133144 Timestamp [UCT]: 2024-08-08 16:05:44 Age [y:d:h:m:s]: 01:089:13:16:49
Block: 1083527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322463 RingCT/type: yes/0
Extra: 01f7b6600f109feb7bf6c0e2ec67a1ee23042dcefe9932cab5af01a656bfb4ca8c021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9ac8b23c4caf84d8899cebad02f954223f53f6cbfb8f1fcb69c5af700c3fc8c 0.600000000000 1557482 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": 1083537, "vin": [ { "gen": { "height": 1083527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9ac8b23c4caf84d8899cebad02f954223f53f6cbfb8f1fcb69c5af700c3fc8c" } } ], "extra": [ 1, 247, 182, 96, 15, 16, 159, 235, 123, 246, 192, 226, 236, 103, 161, 238, 35, 4, 45, 206, 254, 153, 50, 202, 181, 175, 1, 166, 86, 191, 180, 202, 140, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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