← previous blocknext block →recent activity
Analyzing
Block #89,387,110
22 transactions · 17 stateful · 2026-07-22 08:33:48 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,387,110 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w18w09w112w013w015w217w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee4fe1f7…3ead
0x34b655…2a6f
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0b05d77e…6f90
0x34b655…2a6f
4 touches
1 conflict
0x153d1e25…10ea
0x34b655…2a6f
4 touches
1 conflict
0x24bb3547…c78e
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 0xee4fe1f73e…483ead
Audit this contract →
← previous block·next block →recent activity