← previous blocknext block →recent activity
Analyzing
Block #93,405,248
18 transactions · 15 stateful · 2026-08-05 17:21:14 UTC
Parallelism
89/100
Blocked
33%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,405,248 · 18 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
1w03w04w15w06w18w19w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0610892c…fee0
0x34b655…2a6f
4 touches
1 conflict
0x0cc65720…396c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x5484fc7f…a8d8
0x34b655…2a6f
4 touches
1 conflict
0x5af7edb9…23d8
0x34b655…2a6f
4 touches
1 conflict
0x67209a5a…ab0e
0x34b655…2a6f
4 touches
1 conflict
0x707807ff…7edb
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
1 conflict on slot 0x0610892c7c…7cfee0
Audit this contract →
← previous block·next block →recent activity