Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32e0117cc528d5d82ca126b8b73e7d7b53e59141fe35eb52efa3cc25dac7f438

Tx prefix hash: becee64d9234eb3a0c666039d08e71017f8855fd5bcb50dbdf2f895ad87ee693
Tx public key: 49143a75ead3d9f40050ab4cb469ccc49d08ed2d7fd46f1be053cb94142b94db
Timestamp: 1760298280 Timestamp [UCT]: 2025-10-12 19:44:40 Age [y:d:h:m:s]: 00:029:17:42:36
Block: 1388531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21295 RingCT/type: yes/0
Extra: 0149143a75ead3d9f40050ab4cb469ccc49d08ed2d7fd46f1be053cb94142b94db021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b74d2b73ceb8adb590cdc4bdcc494eb472251a0a9d6292ed85dfaeab544f4cdf 0.600000000000 1876746 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": 1388541, "vin": [ { "gen": { "height": 1388531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b74d2b73ceb8adb590cdc4bdcc494eb472251a0a9d6292ed85dfaeab544f4cdf" } } ], "extra": [ 1, 73, 20, 58, 117, 234, 211, 217, 244, 0, 80, 171, 76, 180, 105, 204, 196, 157, 8, 237, 45, 127, 212, 111, 27, 224, 83, 203, 148, 20, 43, 148, 219, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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