Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26dce3d2f84bad929157e54d1c8cc4e262a3df6f39cc6ecc0b7aecfb26bc09e0

Tx prefix hash: f242a27b0a35632b86f2e7fb2ae9a7d87b814cd1de10c9b83c78624899288ee9
Tx public key: 1c950c0fb33ce97055a55e4c124a72ade0401a176a2e9c9f97f46db306e671e0
Timestamp: 1732495110 Timestamp [UCT]: 2024-11-25 00:38:30 Age [y:d:h:m:s]: 00:132:22:25:07
Block: 1161050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94804 RingCT/type: yes/0
Extra: 011c950c0fb33ce97055a55e4c124a72ade0401a176a2e9c9f97f46db306e671e00211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4141f4dade8aa9124b03bea6c4ed9b4dca8218abf8040711658f6c0175859f0 0.600000000000 1646701 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": 1161060, "vin": [ { "gen": { "height": 1161050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4141f4dade8aa9124b03bea6c4ed9b4dca8218abf8040711658f6c0175859f0" } } ], "extra": [ 1, 28, 149, 12, 15, 179, 60, 233, 112, 85, 165, 94, 76, 18, 74, 114, 173, 224, 64, 26, 23, 106, 46, 156, 159, 151, 244, 109, 179, 6, 230, 113, 224, 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