Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11693e0c1a7f3e28d1dfcc0dfdf78d0d5b984ae1543a810fa1b657e100af94a6

Tx prefix hash: 43b04904f06c7ae55977a2f3c1959f4bdef6ef897e289dc2906d188863dc33f9
Tx public key: a4e554c4604106436bd842c3b692f1e618ac868404560654a344c3a1b8ec0ecc
Timestamp: 1704970589 Timestamp [UCT]: 2024-01-11 10:56:29 Age [y:d:h:m:s]: 01:070:13:25:11
Block: 932939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311524 RingCT/type: yes/0
Extra: 01a4e554c4604106436bd842c3b692f1e618ac868404560654a344c3a1b8ec0ecc0211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50bf4c4b5705cd49473e7b48986d448575ddfac85e15e2446aa392ad111344c2 0.600000000000 1390879 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": 932949, "vin": [ { "gen": { "height": 932939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50bf4c4b5705cd49473e7b48986d448575ddfac85e15e2446aa392ad111344c2" } } ], "extra": [ 1, 164, 229, 84, 196, 96, 65, 6, 67, 107, 216, 66, 195, 182, 146, 241, 230, 24, 172, 134, 132, 4, 86, 6, 84, 163, 68, 195, 161, 184, 236, 14, 204, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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