← previous blocknext block →recent activity
Analyzing
Block #98,059,137
31 transactions · 21 stateful · 2026-08-22 01:15:46 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,059,137 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w07w08w016w018w120w122w123w225w326w027w130w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
4 touches
1 conflict
0x00f7e3b7…e017
0x188d58…ea8e
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x52cf5603…ca01
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