← previous blocknext block →recent activity
Analyzing
Block #89,675,962
16 transactions · 16 stateful · 2026-07-23 16:12:56 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,675,962 · 16 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
1w02w03w17w08w19w210w311w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x05c3bda4…de90
0x34b655…2a6f
4 touches
1 conflict
0x12bdece2…85bc
0x34b655…2a6f
4 touches
1 conflict
0x242de003…36c3
0x34b655…2a6f
4 touches
1 conflict
0x25d52624…f992
0x34b655…2a6f
4 touches
1 conflict
0x268f1193…796b
0x34b655…2a6f
4 touches
1 conflict
0x2c2801e1…1c8b
0x34b655…2a6f
4 touches
1 conflict
0x3e505a15…70f8
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity