← previous blocknext block →recent activity
Analyzing
Block #100,983,700
23 transactions · 20 stateful · 2026-09-01 07:34:12 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.87
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,983,700 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w110w215w316w417w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x8b7fe709…9d99
0x34b655…2a6f
8 touches
6 conflicts
0xf91dc591…97cd
0x34b655…2a6f
6 touches
3 conflicts
0xf51ec09c…b4a9
0x34b655…2a6f
6 touches
3 conflicts
0xb409e204…89ac
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity