← previous blocknext block →recent activity
Analyzing
Block #98,568,876
16 transactions · 16 stateful · 2026-08-23 20:14:37 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,568,876 · 16 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
4w08w09w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec1f8387…c83d
0x34b655…2a6f
4 touches
1 conflict
0x3ae7cc07…6f6e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0xdfc400dc…a9b5
0x34b655…2a6f
2 touches
0 conflicts
0xf8c9546a…ebba
0x34b655…2a6f
2 touches
0 conflicts
0xa714c249…26c2
0x67d1be…196f
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 0xec1f838733…a8c83d
Audit this contract →
← previous block·next block →recent activity