← previous blocknext block →recent activity
Analyzing
Block #99,938,373
17 transactions · 14 stateful · 2026-08-28 15:49:54 UTC
Parallelism
82/100
Blocked
43%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,938,373 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w07w18w29w110w012w114w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f25ebf2…13d7
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1f396cee…862f
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x66cc1603…a103
0x34b655…2a6f
4 touches
1 conflict
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0xc0bfcd71…304b
0x851145…3f07
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: Perpl
3 conflicts on slot 0x7f25ebf20a…8a13d7
Audit this contract →
← previous block·next block →recent activity