← previous blocknext block →recent activity
Analyzing
Block #100,141,271
22 transactions · 21 stateful · 2026-08-29 08:51:44 UTC
Parallelism
59/100
Blocked
62%
Avg conflicts / tx
2.09
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,141,271 · 22 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w08w19w110w211w312w413w514w615w717w819w820w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e737223…2278
0x34b655…2a6f
14 touches
21 conflicts
0xa11b60f7…8e8b
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x1d0f9e2e…9742
0x34b655…2a6f
12 touches
15 conflicts
0x51a18c44…1398
0x34b655…2a6f
8 touches
6 conflicts
0xa169711f…c7f3
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x5fad6fee…7714
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
21 conflicts on slot 0x1e737223a3…202278
Audit this contract →
← previous block·next block →recent activity