← previous blocknext block →recent activity
Analyzing
Block #98,471,931
22 transactions · 21 stateful · 2026-08-23 11:53:42 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,471,931 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w17w29w310w411w412w513w517w520w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x705a9a1a…db08
0x34b655…2a6f
8 touches
6 conflicts
0x8a5da891…7442
0x34b655…2a6f
6 touches
3 conflicts
0x94789504…4524
0x34b655…2a6f
6 touches
3 conflicts
0x344ba98e…d204
0x34b655…2a6f
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x1c389468…6b0e
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity