← previous blocknext block →recent activity
Analyzing
Block #90,891,615
14 transactions · 12 stateful · 2026-07-27 22:31:47 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,891,615 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w110w211w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc53838dd…85c9
0x34b655…2a6f
8 touches
6 conflicts
0xff68510a…09f1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x32f99061…edbc
0x34b655…2a6f
4 touches
1 conflict
0x55ce57a3…f7d1
0x34b655…2a6f
4 touches
1 conflict
0x5ac07498…89ee
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
6 conflicts on slot 0xc53838ddd7…b885c9
Audit this contract →
← previous block·next block →recent activity