Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65e2e24aca43a16856c741e82f18df7a8976920fb35b1a5e01af31256d067d66

Tx prefix hash: d75d997ee3c2ff41484d6aed92578118387cd006a157f16020a18baa4bc0c4f3
Tx public key: a3f072001b8a028dade3b6b8ad5ffe338a30e740bea6227794b7a252b99f70de
Timestamp: 1704251566 Timestamp [UCT]: 2024-01-03 03:12:46 Age [y:d:h:m:s]: 01:306:03:53:13
Block: 926986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477640 RingCT/type: yes/0
Extra: 01a3f072001b8a028dade3b6b8ad5ffe338a30e740bea6227794b7a252b99f70de0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 254b3d8bdd638ea4a85a08848e30045b6a1b72e9f946dfa4e08e4737ac0b9fb3 0.600000000000 1384786 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": 926996, "vin": [ { "gen": { "height": 926986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "254b3d8bdd638ea4a85a08848e30045b6a1b72e9f946dfa4e08e4737ac0b9fb3" } } ], "extra": [ 1, 163, 240, 114, 0, 27, 138, 2, 141, 173, 227, 182, 184, 173, 95, 254, 51, 138, 48, 231, 64, 190, 166, 34, 119, 148, 183, 162, 82, 185, 159, 112, 222, 2, 17, 0, 0, 0, 1, 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