Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fb633e43d5bc1e0adc076689606cd4fc6cddaa9971d35b2590d3b6f42aaf9f1

Tx prefix hash: 3e11959ffa173377ac581e6095cb409487e84eaa619e955d1d8db0aa506eebd7
Tx public key: 746ecd526855f84667c4ca167b4f0640a52d5b200e4245ad3bf6c98933829f2a
Timestamp: 1757668808 Timestamp [UCT]: 2025-09-12 09:20:08 Age [y:d:h:m:s]: 00:115:13:24:14
Block: 1366733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82773 RingCT/type: yes/0
Extra: 01746ecd526855f84667c4ca167b4f0640a52d5b200e4245ad3bf6c98933829f2a02110000000cb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce539c5999ef1705d227161c74e21ce48a2d1c5b2952a92562afe6a65d509e16 0.600000000000 1854772 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": 1366743, "vin": [ { "gen": { "height": 1366733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce539c5999ef1705d227161c74e21ce48a2d1c5b2952a92562afe6a65d509e16" } } ], "extra": [ 1, 116, 110, 205, 82, 104, 85, 248, 70, 103, 196, 202, 22, 123, 79, 6, 64, 165, 45, 91, 32, 14, 66, 69, 173, 59, 246, 201, 137, 51, 130, 159, 42, 2, 17, 0, 0, 0, 12, 178, 247, 132, 196, 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