Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d2f084a75f0df2a62146fd3af2819255cb49a82a08014f8f1bc9b3bf8b22166

Tx prefix hash: 06a045e6a8dd7cdf4960a326af0e3247e9b430ad07fc6263225eb6320555a9e7
Tx public key: bc55fad7fe3386a4c9c768ba1487b68552c822c1505e26d5164dcf2a10f5bcb0
Timestamp: 1705762758 Timestamp [UCT]: 2024-01-20 14:59:18 Age [y:d:h:m:s]: 00:245:02:17:06
Block: 939488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175595 RingCT/type: yes/0
Extra: 01bc55fad7fe3386a4c9c768ba1487b68552c822c1505e26d5164dcf2a10f5bcb002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51f5fae2414dc06754f1e3d31db02cffd71dd4f3b41184c93a3e513d15fb0d4e 0.600000000000 1397596 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": 939498, "vin": [ { "gen": { "height": 939488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51f5fae2414dc06754f1e3d31db02cffd71dd4f3b41184c93a3e513d15fb0d4e" } } ], "extra": [ 1, 188, 85, 250, 215, 254, 51, 134, 164, 201, 199, 104, 186, 20, 135, 182, 133, 82, 200, 34, 193, 80, 94, 38, 213, 22, 77, 207, 42, 16, 245, 188, 176, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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