← previous blocknext block →recent activity
Analyzing
Block #100,634,891
18 transactions · 16 stateful · 2026-08-31 02:19:12 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,634,891 · 18 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
4w05w06w17w28w19w310w412w417w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x641aed07…bcb9
0x34b655…2a6f
8 touches
6 conflicts
0x21b468a8…f015
0x34b655…2a6f
8 touches
6 conflicts
0x5684aadd…8d62
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 conflicts
0x8e7fd942…c379
0x34b655…2a6f
4 touches
1 conflict
0x9ad325f5…cc43
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 0x641aed075a…00bcb9
Audit this contract →
← previous block·next block →recent activity