← previous blocknext block →recent activity
Analyzing
Block #100,137,085
15 transactions · 14 stateful · 2026-08-29 08:30:39 UTC
Parallelism
47/100
Blocked
57%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,137,085 · 15 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
1w02w15w16w27w39w410w511w613w014w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbd3c598…8a21
0x34b655…2a6f
8 touches
6 conflicts
0x2cfe7c05…2b42
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x53f7214d…8ec6
0x34b655…2a6f
6 touches
3 conflicts
0x1045386d…cb8b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf06fce24…887d
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 0xfbd3c5980d…718a21
Audit this contract →
← previous block·next block →recent activity