Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 433fb2c26d6db14d040c42a1a4ff18a89024459c9da0e3ef77001c644c191af7

Tx prefix hash: dbd998bf4a6ed2eb399d97f1ba1a55d3ea99cabd04723883c218c63d32dd2b2d
Tx public key: c065cf30363d30f61dcbb0600d199c53a1bc4eb54115bbdf03aa8e0d26c739d3
Timestamp: 1731848438 Timestamp [UCT]: 2024-11-17 13:00:38 Age [y:d:h:m:s]: 00:139:04:25:40
Block: 1155684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99305 RingCT/type: yes/0
Extra: 01c065cf30363d30f61dcbb0600d199c53a1bc4eb54115bbdf03aa8e0d26c739d3021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af22401b46804154124b4a76a14457a1a300b522f6a10866a6d8011ff0e08def 0.600000000000 1641301 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": 1155694, "vin": [ { "gen": { "height": 1155684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af22401b46804154124b4a76a14457a1a300b522f6a10866a6d8011ff0e08def" } } ], "extra": [ 1, 192, 101, 207, 48, 54, 61, 48, 246, 29, 203, 176, 96, 13, 25, 156, 83, 161, 188, 78, 181, 65, 21, 187, 223, 3, 170, 142, 13, 38, 199, 57, 211, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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