← previous blocknext block →recent activity
Analyzing
Block #89,860,994
10 transactions · 9 stateful · 2026-07-24 07:46:40 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,860,994 · 10 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
3w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc516fef7…841c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x119fe5ac…09be
0x34b655…2a6f
4 touches
1 conflict
0x70cfbacf…5c46
0x34b655…2a6f
4 touches
1 conflict
0x1104dd1a…dbcd
0x34b655…2a6f
2 touches
0 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
2 touches
0 conflicts
0x2127ebd5…7b99
0x34b655…2a6f
2 touches
0 conflicts
0x27754bd4…96ae
0x34b655…2a6f
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 0xc516fef749…a5841c
Audit this contract →
← previous block·next block →recent activity