← previous blocknext block →recent activity
Analyzing
Block #100,730,116
23 transactions · 22 stateful · 2026-08-31 10:18:13 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,730,116 · 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
2w04w15w27w19w210w311w412w513w615w616w722w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81716ce9…095f
0x34b655…2a6f
16 touches
28 conflicts
0x970dd6ca…827a
0x34b655…2a6f
12 touches
15 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
12 touches
15 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
12 touches
15 conflicts
0xfb856b8c…7557
0x34b655…2a6f
10 touches
10 conflicts
0x14342429…3353
0x34b655…2a6f
10 touches
10 conflicts
0x79347b24…9fba
0x34b655…2a6f
10 touches
10 conflicts
0xd253497b…a3db
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0x81716ce924…61095f
Audit this contract →
← previous block·next block →recent activity