← previous blocknext block →recent activity
Analyzing
Block #98,841,149
14 transactions · 13 stateful · 2026-08-24 19:27:28 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,841,149 · 14 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
2w03w16w07w19w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1ac5a56…17d8
0x99c7a7…8bf0
4 touches
1 conflict
0x72083f0d…082a
0x34b655…2a6f
4 touches
1 conflict
0x7a78336e…dd1e
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xb1856468…e84f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x49f39582…ccc7
0x754704…b603
4 touches
1 conflict
0x53e67340…60f7
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: 0x99c7a72e…c78bf0
1 conflict on slot 0xa1ac5a568a…af17d8
Audit this contract →
← previous block·next block →recent activity