Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed25f9d9dc60dd9ff73e9534b0fceef09aed105f9b0b8981311bb7384f02d594

Tx prefix hash: 52d7c5069b00e0688f50cf16fc5027d69d67a84dd936a74ef1d762bf487c5aed
Tx public key: dfca0ffd4b2afc4bdb5ba426745eb5ec00b6d06fd2a97a4585fb11118afa2bba
Timestamp: 1724731069 Timestamp [UCT]: 2024-08-27 03:57:49 Age [y:d:h:m:s]: 00:089:03:36:17
Block: 1096767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63774 RingCT/type: yes/0
Extra: 01dfca0ffd4b2afc4bdb5ba426745eb5ec00b6d06fd2a97a4585fb11118afa2bba021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3ad266c2567c01598c46f007d93ab3dc2e0ea8449287ae2f73ec5f9d5e7cf11 0.600000000000 1571962 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": 1096777, "vin": [ { "gen": { "height": 1096767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3ad266c2567c01598c46f007d93ab3dc2e0ea8449287ae2f73ec5f9d5e7cf11" } } ], "extra": [ 1, 223, 202, 15, 253, 75, 42, 252, 75, 219, 91, 164, 38, 116, 94, 181, 236, 0, 182, 208, 111, 210, 169, 122, 69, 133, 251, 17, 17, 138, 250, 43, 186, 2, 17, 0, 0, 0, 5, 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