Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c9e804df37118c1b703672942cd421a244b410f08517f450f8ec2fe030b4be8

Tx prefix hash: dc165eab02eaa3915514eac6e0831309e5ef33250778fc29082f5c3d74ecb84d
Tx public key: 8bcec4e4a3a3ece202750c05d18df2d2fbff91e91290afd36a79f18c59693bb8
Timestamp: 1755129568 Timestamp [UCT]: 2025-08-13 23:59:28 Age [y:d:h:m:s]: 00:053:01:17:50
Block: 1346361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37314 RingCT/type: yes/0
Extra: 018bcec4e4a3a3ece202750c05d18df2d2fbff91e91290afd36a79f18c59693bb8021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe3f5fb9f7b504a32debfe31874d7d43970cdf30c8a0320e12b36e157f63bc43 0.600000000000 1834260 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": 1346371, "vin": [ { "gen": { "height": 1346361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe3f5fb9f7b504a32debfe31874d7d43970cdf30c8a0320e12b36e157f63bc43" } } ], "extra": [ 1, 139, 206, 196, 228, 163, 163, 236, 226, 2, 117, 12, 5, 209, 141, 242, 210, 251, 255, 145, 233, 18, 144, 175, 211, 106, 121, 241, 140, 89, 105, 59, 184, 2, 17, 0, 0, 0, 2, 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