← previous blocknext block →recent activity
Analyzing
Block #94,836,236
17 transactions · 16 stateful · 2026-08-10 17:35:18 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,836,236 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w17w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd30f9e74…d404
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
6 touches
3 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x1c7f2eca…cf5e
0x34b655…2a6f
4 touches
1 conflict
0x6f8644f7…10fa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xd30f9e74d6…9ed404
Audit this contract →
← previous block·next block →recent activity