← previous blocknext block →recent activity
Analyzing
Block #89,694,507
17 transactions · 13 stateful · 2026-07-23 17:46:35 UTC
Parallelism
65/100
Blocked
46%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,694,507 · 17 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
5w06w18w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x553d09ad…e640
0x34b655…2a6f
6 touches
3 conflicts
0xadd9c687…1f8b
0x34b655…2a6f
6 touches
3 conflicts
0x91f687f3…aca8
0x34b655…2a6f
6 touches
3 conflicts
0x508bbf1b…fe95
0x34b655…2a6f
4 touches
1 conflict
0x644ef69c…26e0
0x34b655…2a6f
4 touches
1 conflict
0x6e0e8837…2e59
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity