← previous blocknext block →recent activity
Analyzing
Block #100,917,335
22 transactions · 15 stateful · 2026-09-01 02:00:23 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,917,335 · 22 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
4w05w18w214w015w319w020w121w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce39f2b1…4654
0x34b655…2a6f
6 touches
3 conflicts
0x55192654…91fe
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x3703b3c0…5695
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xce39f2b144…404654
Audit this contract →
← previous block·next block →recent activity