← previous blocknext block →recent activity
Analyzing
Block #98,440,807
9 transactions · 9 stateful · 2026-08-23 09:16:44 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,440,807 · 9 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
4w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf9b3fad…743d
0x8964d7…10f8
4 touches
1 conflict
0xbf9b3fad…743e
0x8964d7…10f8
4 touches
1 conflict
0xbf9b3fad…7440
0x8964d7…10f8
4 touches
1 conflict
0xc05a3651…44e4
0x8964d7…10f8
4 touches
1 conflict
0xc05a3651…44e5
0x8964d7…10f8
4 touches
1 conflict
0xc05a3651…44e8
0x8964d7…10f8
4 touches
1 conflict
0xc05a3651…44e9
0x8964d7…10f8
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
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 0xbf9b3fad9a…55743d
Audit this contract →
← previous block·next block →recent activity