Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0393862075c2342b29fbfe99146c42555b5fcaf2c3a71fc117eb076f81dee417

Tx prefix hash: 60919459584df9601378fe4f7f0ced60ed1e7a194a8ccb7e036196ce29a42e68
Tx public key: 219dfd4dcebafe7e42b3f6eafd263a004053cb82cdd68ad2c760a946b5553edf
Timestamp: 1728443160 Timestamp [UCT]: 2024-10-09 03:06:00 Age [y:d:h:m:s]: 01:032:22:08:53
Block: 1127551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281905 RingCT/type: yes/0
Extra: 01219dfd4dcebafe7e42b3f6eafd263a004053cb82cdd68ad2c760a946b5553edf021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58a390736654033fd4057a8a608bd2fed1aced1fde91ecc84152fe833cf57f56 0.600000000000 1610358 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": 1127561, "vin": [ { "gen": { "height": 1127551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58a390736654033fd4057a8a608bd2fed1aced1fde91ecc84152fe833cf57f56" } } ], "extra": [ 1, 33, 157, 253, 77, 206, 186, 254, 126, 66, 179, 246, 234, 253, 38, 58, 0, 64, 83, 203, 130, 205, 214, 138, 210, 199, 96, 169, 70, 181, 85, 62, 223, 2, 17, 0, 0, 0, 3, 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