Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a63f056e24d4a7ffddbfcf1ff9a75b54cd55b54366f8ab65db7fbbf66e8ccf68

Tx prefix hash: b99aaad710efcd7876e0569df0349434612ba00d8f0d343934dd24ee61b8a649
Tx public key: f9362a40e0cc4cd281a427f5310656d2f558f8e6ec7c13bfe2a4408809da9ed9
Timestamp: 1752598548 Timestamp [UCT]: 2025-07-15 16:55:48 Age [y:d:h:m:s]: 00:163:10:44:17
Block: 1326134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115621 RingCT/type: yes/0
Extra: 01f9362a40e0cc4cd281a427f5310656d2f558f8e6ec7c13bfe2a4408809da9ed9021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d59986d6f386839a0aceb7a345d5e2155eaf107c04d7a15c2dbb2fddc1e3bac 0.600000000000 1813883 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": 1326144, "vin": [ { "gen": { "height": 1326134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d59986d6f386839a0aceb7a345d5e2155eaf107c04d7a15c2dbb2fddc1e3bac" } } ], "extra": [ 1, 249, 54, 42, 64, 224, 204, 76, 210, 129, 164, 39, 245, 49, 6, 86, 210, 245, 88, 248, 230, 236, 124, 19, 191, 226, 164, 64, 136, 9, 218, 158, 217, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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