← previous blocknext block →recent activity
Analyzing
Block #100,430,694
18 transactions · 17 stateful · 2026-08-30 09:11:53 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,430,694 · 18 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
5w07w18w212w013w114w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1db5837f…1264
0x34b655…2a6f
6 touches
3 conflicts
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x3bf4435a…28a2
0x928dc8…8207
4 touches
1 conflict
0x3bf4435a…28a5
0x928dc8…8207
4 touches
1 conflict
0x3bf4435a…28a6
0x928dc8…8207
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
4 touches
1 conflict
0x4b5f2081…f3c5
0x34b655…2a6f
4 touches
1 conflict
0x51f32324…de5c
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
3 conflicts on slot 0x1db5837f6b…d01264
Audit this contract →
← previous block·next block →recent activity