← previous blocknext block →recent activity
Analyzing
Block #88,357,591
31 transactions · 25 stateful · 2026-07-17 13:48:42 UTC
Parallelism
87/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,357,591 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w17w08w19w010w113w214w016w120w123w024w125w228w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x756913cf…e7bd
0xa6afd3…d132
6 touches
3 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
4 touches
1 conflict
0x14420c60…fe42
0x34b655…2a6f
4 touches
1 conflict
0x14420c60…fe43
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x39f0f6b5…57eb
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: 0x48cba278…e2b48b
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity