Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3664c7cf84d4bf6277c504a7b2546f9c61939419d691715859578f9bd0fdebd4

Tx prefix hash: 99bb3231f25c42f5c90d6ce8c094398a4c0fc4cfc7a5a1cadaec906175e2910f
Tx public key: 0709c191cdc31cefa284b4fdae45d31b5482bdf786100d17931405fef0c0187c
Timestamp: 1750146851 Timestamp [UCT]: 2025-06-17 07:54:11 Age [y:d:h:m:s]: 00:156:20:10:53
Block: 1306811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109882 RingCT/type: yes/0
Extra: 010709c191cdc31cefa284b4fdae45d31b5482bdf786100d17931405fef0c0187c021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a20be305e7021478d3f7fd5b8c0f99c0c02f8ce16a89547697d711ee2b37faa2 0.600000000000 1794420 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": 1306821, "vin": [ { "gen": { "height": 1306811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a20be305e7021478d3f7fd5b8c0f99c0c02f8ce16a89547697d711ee2b37faa2" } } ], "extra": [ 1, 7, 9, 193, 145, 205, 195, 28, 239, 162, 132, 180, 253, 174, 69, 211, 27, 84, 130, 189, 247, 134, 16, 13, 23, 147, 20, 5, 254, 240, 192, 24, 124, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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