← previous blocknext block →recent activity
Analyzing
Block #98,723,795
22 transactions · 22 stateful · 2026-08-24 09:36:43 UTC
Parallelism
77/100
Blocked
41%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,723,795 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w112w013w114w215w316w418w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x516e8f31…cd02
0x40c49f…2af0
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x6518075e…2b17
0x2a68ba…90c5
10 touches
10 conflicts
0x71fad9ce…c11f
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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: 0x40c49f17…d22af0
10 conflicts on slot 0x516e8f3167…79cd02
Audit this contract →
← previous block·next block →recent activity