← previous blocknext block →recent activity
Analyzing
Block #90,485,379
18 transactions · 17 stateful · 2026-07-26 12:28:04 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,485,379 · 18 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
2w03w14w05w16w17w210w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x745952b2…d90c
0x34b655…2a6f
8 touches
6 conflicts
0xc244b288…db37
0x34b655…2a6f
6 touches
3 conflicts
0xe6bc2816…1787
0x34b655…2a6f
6 touches
3 conflicts
0x1a5d321d…a474
0x34b655…2a6f
6 touches
3 conflicts
0xf6366f16…1d91
0x34b655…2a6f
6 touches
3 conflicts
0x97529895…5a02
0x34b655…2a6f
6 touches
3 conflicts
0xb9927449…511c
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity