← previous blocknext block →recent activity
Analyzing
Block #98,679,009
19 transactions · 16 stateful · 2026-08-24 05:48:15 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,679,009 · 19 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
1w012w013w115w016w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0fa05bb…dda8
0x8964d7…10f8
4 touches
1 conflict
0xa4a8346a…6981
0x8964d7…10f8
4 touches
1 conflict
0xa4a8346a…6982
0x8964d7…10f8
4 touches
1 conflict
0xa4a8346a…6984
0x8964d7…10f8
4 touches
1 conflict
0xe0fa05bb…dda1
0x8964d7…10f8
4 touches
1 conflict
0xe0fa05bb…dda2
0x8964d7…10f8
4 touches
1 conflict
0xe0fa05bb…dda5
0x8964d7…10f8
4 touches
1 conflict
0xe0fa05bb…dda6
0x8964d7…10f8
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 0xe0fa05bb95…dedda8
Audit this contract →
← previous block·next block →recent activity