← previous blocknext block →recent activity
Analyzing
Block #100,234,344
18 transactions · 16 stateful · 2026-08-29 16:40:14 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,234,344 · 18 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
3w06w17w18w210w311w412w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x8db32935…81a7
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
8 touches
6 conflicts
0x49fc0524…1bad
0x34b655…2a6f
7 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc125f6c9…07f6
0x34b655…2a6f
6 touches
3 conflicts
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