← previous blocknext block →recent activity
Analyzing
Block #99,872,735
21 transactions · 17 stateful · 2026-08-28 10:19:08 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,872,735 · 21 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
5w06w19w210w314w419w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e412bc8…7513
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xd7668c61…55f8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0490581d…adaf
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
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: Perpl
6 conflicts on slot 0x4e412bc81f…ef7513
Audit this contract →
← previous block·next block →recent activity