Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e17f420fd06902498e7039b2f98975006088c8175c45e9b3c7c84ed59319a0a

Tx prefix hash: e201957cc4fd1276c79c1e6ec73d9db886d3f9399bdf3fd30682a044feb2bef2
Tx public key: f39344e8151af7c533785a5901d852d4250f9d696d7772a18212fe9b6aca37d1
Timestamp: 1720175836 Timestamp [UCT]: 2024-07-05 10:37:16 Age [y:d:h:m:s]: 00:331:10:34:00
Block: 1059009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236869 RingCT/type: yes/0
Extra: 01f39344e8151af7c533785a5901d852d4250f9d696d7772a18212fe9b6aca37d10211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75fecf4ed4b36dd7f3983f389f998092b34eacf6d1da44126d8fda22cdb86fc8 0.600000000000 1529468 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": 1059019, "vin": [ { "gen": { "height": 1059009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75fecf4ed4b36dd7f3983f389f998092b34eacf6d1da44126d8fda22cdb86fc8" } } ], "extra": [ 1, 243, 147, 68, 232, 21, 26, 247, 197, 51, 120, 90, 89, 1, 216, 82, 212, 37, 15, 157, 105, 109, 119, 114, 161, 130, 18, 254, 155, 106, 202, 55, 209, 2, 17, 0, 0, 0, 5, 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