← previous blocknext block →recent activity
Analyzing
Block #98,567,875
15 transactions · 15 stateful · 2026-08-23 20:09:23 UTC
Parallelism
87/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,567,875 · 15 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
2w09w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f8068fd…4720
0x8964d7…10f8
4 touches
1 conflict
0x9f8068fd…4722
0x8964d7…10f8
4 touches
1 conflict
0xb8c410c4…68a2
0x8964d7…10f8
4 touches
1 conflict
0xb8c410c4…68a3
0x8964d7…10f8
4 touches
1 conflict
0xb8c410c4…68a6
0x8964d7…10f8
4 touches
1 conflict
0xb8c410c4…68a7
0x8964d7…10f8
4 touches
1 conflict
0xb8c410c4…68a8
0x8964d7…10f8
4 touches
1 conflict
0x152a2f3e…13f8
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 0x9f8068fdd4…ad4720
Audit this contract →
← previous block·next block →recent activity