← previous blocknext block →recent activity
Analyzing
Block #90,855,549
12 transactions · 11 stateful · 2026-07-27 19:30:18 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,855,549 · 12 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
5w06w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa47b7766…ee6e
0x34b655…2a6f
4 touches
1 conflict
0xa9942473…84c6
0x34b655…2a6f
4 touches
1 conflict
0x0b0c2e8d…c1b8
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x22143977…85aa
0xe52b14…7230
3 touches
1 conflict
0x5f188956…44a6
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4ab
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 0xa47b776601…7cee6e
Audit this contract →
← previous block·next block →recent activity