← previous blocknext block →recent activity
Analyzing
Block #94,911,838
29 transactions · 12 stateful · 2026-08-10 23:55:33 UTC
Parallelism
93/100
Blocked
8%
Avg conflicts / tx
0.03
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,911,838 · 29 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
16w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38bdc5d3…a632
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x0603347b…5872
0x34b655…2a6f
2 touches
0 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
2 touches
0 conflicts
0x09056a1b…ef8b
0x34b655…2a6f
2 touches
0 conflicts
0x0dd7d6d8…3700
0x34b655…2a6f
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 0x38bdc5d3e1…01a632
Audit this contract →
← previous block·next block →recent activity