← previous blocknext block →recent activity
Analyzing
Block #88,365,364
22 transactions · 19 stateful · 2026-07-17 14:41:00 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,365,364 · 22 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
2w08w011w112w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f900be0…cd6e
0x34b655…2a6f
4 touches
1 conflict
0x957c875f…b3f9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xed5b6663…76fa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x70da80f3…a8f7
0x851145…3f07
4 touches
1 conflict
0xd2052f35…5428
0x851145…3f07
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
1 conflict on slot 0x6f900be04d…4ccd6e
Audit this contract →
← previous block·next block →recent activity