← previous blocknext block →recent activity
Analyzing
Block #98,847,740
25 transactions · 24 stateful · 2026-08-24 20:00:37 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,847,740 · 25 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
1w02w13w04w110w011w113w115w016w017w218w119w222w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f63dad0…0d10
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0f4998fe…6a62
0x34b655…2a6f
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x64a785e4…0110
0x34b655…2a6f
4 touches
1 conflict
0x6938f481…8f24
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x4f63dad026…270d10
Audit this contract →
← previous block·next block →recent activity