← previous blocknext block →recent activity
Analyzing
Block #91,018,619
10 transactions · 10 stateful · 2026-07-28 09:11:30 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,018,619 · 10 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
3w04w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x571aa8b4…35fa
0x34b655…2a6f
4 touches
1 conflict
0xbbeac3b7…c14b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x865229e7…9846
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xa535ecc7…c0e0
0x34b655…2a6f
2 touches
0 conflicts
0xa80684c9…3948
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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 0x571aa8b49c…9035fa
Audit this contract →
← previous block·next block →recent activity