← previous blocknext block →recent activity
Analyzing
Block #98,065,661
21 transactions · 17 stateful · 2026-08-22 01:48:36 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,065,661 · 21 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
2w07w08w19w010w118w019w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x01a08f7d…dec6
0x34b655…2a6f
4 touches
1 conflict
0x0358eb3f…80dd
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x2d541549…9cce
0x34b655…2a6f
4 touches
1 conflict
0x48a0f121…953b
0x34b655…2a6f
4 touches
1 conflict
0x52d8de8c…d609
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity