← previous blocknext block →recent activity
Analyzing
Block #90,624,410
12 transactions · 11 stateful · 2026-07-27 00:07:25 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,624,410 · 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
3w05w18w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x8f518381…ae20
0x34b655…2a6f
4 touches
1 conflict
0x089dbaf9…51c9
0x065c9d…c394
2 touches
0 conflicts
0x26c79806…d851
0x065c9d…c394
2 touches
0 conflicts
0x54380f32…7aa9
0x065c9d…c394
2 touches
0 conflicts
0x92265121…fb96
0x065c9d…c394
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity