← previous blocknext block →recent activity
Analyzing
Block #93,656,640
20 transactions · 19 stateful · 2026-08-06 14:25:01 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,656,640 · 20 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
1w02w03w14w26w37w411w112w415w017w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7d9fbdca…c1f1
0x34b655…2a6f
8 touches
6 conflicts
0x5d1ac445…5233
0x34b655…2a6f
6 touches
3 conflicts
0x134411c7…4619
0x851145…3f07
4 touches
1 conflict
0x41f1e2e5…2edf
0x34b655…2a6f
4 touches
1 conflict
0x74085d0a…612d
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity