← previous blocknext block →recent activity
Analyzing
Block #100,894,546
22 transactions · 19 stateful · 2026-09-01 00:05:45 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
1.36
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,894,546 · 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
1w02w18w19w210w312w414w515w616w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf38a3927…ad62
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xca162e51…ea79
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd25997d0…a687
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x08e8f2c9…a11a
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
21 conflicts on slot 0xf38a392760…8fad62
Audit this contract →
← previous block·next block →recent activity