Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b0bec20fc03065aa4cdebace7ee241706393d9be255e19ad6b0614ac0b3f7ac

Tx prefix hash: e6e436a4c5b3e8107f4ffe063c758a5cfbb0d08af50ea6d76876a65a5a7f272f
Tx public key: 34bf5e185de4f88579fd791f1b2279f0ae7a897b2abcc26d51af18b640134747
Timestamp: 1761820704 Timestamp [UCT]: 2025-10-30 10:38:24 Age [y:d:h:m:s]: 00:009:19:01:11
Block: 1401169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6991 RingCT/type: yes/0
Extra: 0134bf5e185de4f88579fd791f1b2279f0ae7a897b2abcc26d51af18b640134747021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aee10f7ac06f586149dffb24a4b8d1ea7e212cf19721b2993aa33fda3d2298cc 0.600000000000 1889488 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": 1401179, "vin": [ { "gen": { "height": 1401169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aee10f7ac06f586149dffb24a4b8d1ea7e212cf19721b2993aa33fda3d2298cc" } } ], "extra": [ 1, 52, 191, 94, 24, 93, 228, 248, 133, 121, 253, 121, 31, 27, 34, 121, 240, 174, 122, 137, 123, 42, 188, 194, 109, 81, 175, 24, 182, 64, 19, 71, 71, 2, 17, 0, 0, 0, 1, 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