← previous blocknext block →recent activity
Analyzing
Block #88,360,360
24 transactions · 19 stateful · 2026-07-17 14:07:19 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,360,360 · 24 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
1w02w03w111w113w014w015w116w017w118w119w021w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xe7e223bb…12db
0x0a2fbf…29b1
4 touches
1 conflict
0xfcf4c557…0b2e
0x0a2fbf…29b1
4 touches
1 conflict
0x01e39429…f244
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d8
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d9
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 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity