← previous blocknext block →recent activity
Analyzing
Block #100,978,129
24 transactions · 17 stateful · 2026-09-01 07:06:11 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,978,129 · 24 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
1w03w04w15w06w07w18w219w320w421w522w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedd439ee…048d
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x9a100e05…c541
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8b7fe709…9d99
0x34b655…2a6f
6 touches
3 conflicts
0x32c3536c…e1c1
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
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 0xedd439ee2e…74048d
Audit this contract →
← previous block·next block →recent activity