Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e2268a287fcc0e1fd598966c7f77593e193a344e7b457cff2e16a64fed30a69

Tx prefix hash: eee998d45eb08a673a3060a5285f8bc252681ec643af17ed5e2863ef9f4600bc
Tx public key: 1124d9d30d2bc82d97d051a937a6e415b03c59fa97734dbc6fa2a84f68674cff
Timestamp: 1730363372 Timestamp [UCT]: 2024-10-31 08:29:32 Age [y:d:h:m:s]: 01:009:22:45:01
Block: 1143405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265524 RingCT/type: yes/0
Extra: 011124d9d30d2bc82d97d051a937a6e415b03c59fa97734dbc6fa2a84f68674cff0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2cd4af9bea16f34a5417d346d4a9c14b42715efcc99957b50e64cdaccebe0ea 0.600000000000 1627276 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": 1143415, "vin": [ { "gen": { "height": 1143405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2cd4af9bea16f34a5417d346d4a9c14b42715efcc99957b50e64cdaccebe0ea" } } ], "extra": [ 1, 17, 36, 217, 211, 13, 43, 200, 45, 151, 208, 81, 169, 55, 166, 228, 21, 176, 60, 89, 250, 151, 115, 77, 188, 111, 162, 168, 79, 104, 103, 76, 255, 2, 17, 0, 0, 0, 9, 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