← previous blocknext block →recent activity
Analyzing
Block #90,541,161
16 transactions · 16 stateful · 2026-07-26 17:08:38 UTC
Parallelism
63/100
Blocked
31%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,541,161 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w28w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x114324a9…6d5e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x344bc09a…942f
0x34b655…2a6f
4 touches
1 conflict
0x3c1390ae…035a
0x34b655…2a6f
4 touches
1 conflict
0x3e30f1bf…6453
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
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 0x114324a9e9…dd6d5e
Audit this contract →
← previous block·next block →recent activity