← previous blocknext block →recent activity
Analyzing
Block #98,079,781
40 transactions · 26 stateful · 2026-08-22 02:59:40 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,079,781 · 40 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w015w016w017w126w127w228w332w236w337w439w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xa02838a3…bc54
0x34b655…2a6f
8 touches
6 conflicts
0x62910921…3016
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xa84f8da4…4839
0x34b655…2a6f
6 touches
3 conflicts
0x3fcb5bac…74b8
0x34b655…2a6f
4 touches
1 conflict
0x53d95ea5…b09b
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
6 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity