← previous blocknext block →recent activity
Analyzing
Block #93,365,375
18 transactions · 15 stateful · 2026-08-05 14:00:45 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,365,375 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w18w29w213w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3932086f…b68b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
4 touches
1 conflict
0x04e17b28…d9ef
0x34b655…2a6f
4 touches
1 conflict
0x2fd12b6c…02cc
0x34b655…2a6f
4 touches
1 conflict
0x4e50038e…6e29
0x34b655…2a6f
4 touches
1 conflict
0x58d61c09…43b8
0x34b655…2a6f
4 touches
1 conflict
0x6a05e78d…283e
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
3 conflicts on slot 0x3932086f6a…a5b68b
Audit this contract →
← previous block·next block →recent activity