← previous blocknext block →recent activity
Analyzing
Block #98,365,113
13 transactions · 12 stateful · 2026-08-23 02:55:55 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,365,113 · 13 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
1w03w06w17w28w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x522acad4…5db3
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x631583cf…bf21
0x34b655…2a6f
6 touches
3 conflicts
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0x4e135144…4167
0x34b655…2a6f
4 touches
1 conflict
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0x00f6a8a7…0e6e
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 0x522acad47c…6b5db3
Audit this contract →
← previous block·next block →recent activity