← previous blocknext block →recent activity
Analyzing
Block #89,759,383
19 transactions · 16 stateful · 2026-07-23 23:14:03 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,759,383 · 19 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
6w07w18w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafe72ad3…c5fa
0x34b655…2a6f
4 touches
1 conflict
0x0b0c2e8d…c1b8
0xe52b14…7230
4 touches
1 conflict
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x6f0bcd4a…24f5
0xe52b14…7230
3 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…721b
0x34b655…2a6f
2 touches
0 conflicts
0xbb96f8af…205f
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 0xafe72ad3a4…74c5fa
Audit this contract →
← previous block·next block →recent activity