← previous blocknext block →recent activity
Analyzing
Block #93,366,439
17 transactions · 16 stateful · 2026-08-05 14:06:06 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,366,439 · 17 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
1w03w14w05w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c390858…b1ed
0x34b655…2a6f
4 touches
1 conflict
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0xac8a5059…fd42
0x34b655…2a6f
4 touches
1 conflict
0x211d520a…bf67
0x34b655…2a6f
2 touches
0 conflicts
0x33c49d59…9997
0x34b655…2a6f
2 touches
0 conflicts
0x3786a2d7…4c21
0x34b655…2a6f
2 touches
0 conflicts
0x48315f67…c1a6
0x34b655…2a6f
2 touches
0 conflicts
0x52e88fc2…bbcf
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 0x2c3908588c…50b1ed
Audit this contract →
← previous block·next block →recent activity