← previous blocknext block →recent activity
Analyzing
Block #88,340,128
13 transactions · 12 stateful · 2026-07-17 11:51:27 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,340,128 · 13 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
6w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92b49f44…ee4f
0x34b655…2a6f
4 touches
1 conflict
0xbd693ff4…5072
0x34b655…2a6f
4 touches
1 conflict
0xd03a15ef…6c9a
0x34b655…2a6f
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x06c980ab…5577
0x34b655…2a6f
2 touches
0 conflicts
0x0dfe5bc0…c55f
0x34b655…2a6f
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x50e84e6c…287f
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 0x92b49f44ef…78ee4f
Audit this contract →
← previous block·next block →recent activity