← previous blocknext block →recent activity
Analyzing
Block #98,769,508
20 transactions · 14 stateful · 2026-08-24 13:26:48 UTC
Parallelism
90/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,769,508 · 20 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
5w06w111w012w013w115w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x84ee515e…3347
0x8964d7…10f8
4 touches
1 conflict
0x661bbf09…33c3
0x8964d7…10f8
4 touches
1 conflict
0x661bbf09…33c5
0x8964d7…10f8
4 touches
1 conflict
0x84ee515e…3344
0x8964d7…10f8
4 touches
1 conflict
0x84ee515e…3345
0x8964d7…10f8
4 touches
1 conflict
0x0de7749d…5bef
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x84ee515e87…0b3347
Audit this contract →
← previous block·next block →recent activity