← previous blocknext block →recent activity
Analyzing
Block #100,612,829
20 transactions · 20 stateful · 2026-08-31 00:28:14 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,612,829 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w111w212w313w414w515w316w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a548af5…0eb0
0x34b655…2a6f
12 touches
15 conflicts
0xb0c27941…a6b9
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x155e52ca…fac7
0x34b655…2a6f
6 touches
3 conflicts
0x8c34719c…4d14
0x34b655…2a6f
4 touches
1 conflict
0xdfac3ce0…6699
0x99c7a7…8bf0
4 touches
1 conflict
0x3740f434…cccb
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
15 conflicts on slot 0x5a548af508…f00eb0
Audit this contract →
← previous block·next block →recent activity