← previous blocknext block →recent activity
Analyzing
Block #89,861,620
7 transactions · 6 stateful · 2026-07-24 07:49:49 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,861,620 · 7 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa535ecc7…c0e0
0x34b655…2a6f
4 touches
1 conflict
0x3fa5bab0…2270
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x496ff651…1310
0x34b655…2a6f
3 touches
1 conflict
0xf79c54f3…c0c1
0x34b655…2a6f
3 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
2 touches
0 conflicts
0x3f3d0666…5614
0x34b655…2a6f
2 touches
0 conflicts
0x40fe6af8…53a1
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 0xa535ecc7af…ecc0e0
Audit this contract →
← previous block·next block →recent activity