← previous blocknext block →recent activity
Analyzing
Block #98,582,850
17 transactions · 17 stateful · 2026-08-23 21:27:19 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,582,850 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w210w311w012w115w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xdfce7dfe…5053
0x34b655…2a6f
6 touches
3 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x8db32935…81a7
0x34b655…2a6f
4 touches
1 conflict
0xab707260…67d6
0x34b655…2a6f
4 touches
1 conflict
0xbc78e7a3…04ab
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity