← previous blocknext block →recent activity
Analyzing
Block #95,389,962
17 transactions · 16 stateful · 2026-08-12 16:13:53 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,389,962 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8e1bb47d…34b7
0xd32edf…ff58
3 touches
1 conflict
0x1a15fd30…4b57
0x065c9d…c394
2 touches
0 conflicts
0x3a2f12a4…b93e
0x065c9d…c394
2 touches
0 conflicts
0x650abbae…07f7
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity