← previous blocknext block →recent activity
Analyzing
Block #100,147,406
17 transactions · 16 stateful · 2026-08-29 09:22:37 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,147,406 · 17 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
1w05w16w27w08w19w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b43dd7d…7f99
0x34b655…2a6f
10 touches
10 conflicts
0x739db484…e44a
0x34b655…2a6f
10 touches
10 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
10 touches
10 conflicts
0x42e917f7…ed8c
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xc5401a4c…e71f
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
10 conflicts on slot 0x2b43dd7d55…f37f99
Audit this contract →
← previous block·next block →recent activity