← previous blocknext block →recent activity
Analyzing
Block #90,623,547
17 transactions · 14 stateful · 2026-07-27 00:03:05 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,623,547 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w18w311w413w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce0d3554…d1dd
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7032dc14…49ea
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
3 conflicts on slot 0xce0d3554c7…f2d1dd
Audit this contract →
← previous block·next block →recent activity