← previous blocknext block →recent activity
Analyzing
Block #88,344,497
15 transactions · 15 stateful · 2026-07-17 12:20:40 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,344,497 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w110w011w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f7f7286…d268
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xa6c3f6bf…7fac
0x34b655…2a6f
4 touches
1 conflict
0xab4aea39…fcaa
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0x5f7f728610…fbd268
Audit this contract →
← previous block·next block →recent activity