Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 544055c8899fca53802cc07318a1a8992a4cb568266a0271f46f4851fb7a098e

Tx prefix hash: 004c3e16628d2b251b2a5487c7bac6e06dd1142db0ca869f819b274942e1ee02
Tx public key: 16c00ee00a07d6ffb6aa50d089ce03fc97ea5ff0da74ab412619bc373cb8159a
Timestamp: 1729456762 Timestamp [UCT]: 2024-10-20 20:39:22 Age [y:d:h:m:s]: 00:172:05:13:14
Block: 1135939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122876 RingCT/type: yes/0
Extra: 0116c00ee00a07d6ffb6aa50d089ce03fc97ea5ff0da74ab412619bc373cb8159a0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6956c0276b7e4065c86ddaf413ed4c11473e377c561c2491c3cef39936d9cc6 0.600000000000 1619280 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": 1135949, "vin": [ { "gen": { "height": 1135939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6956c0276b7e4065c86ddaf413ed4c11473e377c561c2491c3cef39936d9cc6" } } ], "extra": [ 1, 22, 192, 14, 224, 10, 7, 214, 255, 182, 170, 80, 208, 137, 206, 3, 252, 151, 234, 95, 240, 218, 116, 171, 65, 38, 25, 188, 55, 60, 184, 21, 154, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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