Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a64c69f7aab259807ba6383fb40cec4c0e56d5bf00595fc9ad508fdd85ab59bd

Tx prefix hash: e11c97d72bdb51a93e2d41c8c97ebf7c50cb65e3b2b568ec67d45acdaf9d323f
Tx public key: 410b7e1a94e24171d0fe25e843342e7901a76b4ced15d4f718f703d45604829b
Timestamp: 1750303626 Timestamp [UCT]: 2025-06-19 03:27:06 Age [y:d:h:m:s]: 00:155:13:28:36
Block: 1308076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109003 RingCT/type: yes/0
Extra: 01410b7e1a94e24171d0fe25e843342e7901a76b4ced15d4f718f703d45604829b021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23a3ffc40cd7ed6d006792e30a104520be4862f6362a5639e2c743361dce088c 0.600000000000 1795689 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": 1308086, "vin": [ { "gen": { "height": 1308076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23a3ffc40cd7ed6d006792e30a104520be4862f6362a5639e2c743361dce088c" } } ], "extra": [ 1, 65, 11, 126, 26, 148, 226, 65, 113, 208, 254, 37, 232, 67, 52, 46, 121, 1, 167, 107, 76, 237, 21, 212, 247, 24, 247, 3, 212, 86, 4, 130, 155, 2, 17, 0, 0, 0, 4, 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