← previous blocknext block →recent activity
Analyzing
Block #88,157,121
19 transactions · 16 stateful · 2026-07-16 15:27:05 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,157,121 · 19 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
2w03w111w012w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a46e23f…d28d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x953517cb…cdec
0x34b655…2a6f
4 touches
1 conflict
0x43fd3667…094b
0x34b655…2a6f
2 touches
0 conflicts
0x66d5e476…8a1f
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 0x6a46e23fa7…c7d28d
Audit this contract →
← previous block·next block →recent activity