← previous blocknext block →recent activity
Analyzing
Block #100,869,762
10 transactions · 8 stateful · 2026-08-31 22:01:06 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,869,762 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x489114d7…436d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xcb99c025…30d8
0x34b655…2a6f
3 touches
1 conflict
0xf29ce086…fc39
0x34b655…2a6f
3 touches
1 conflict
0xe2263bea…6a9e
0x34ae4d…3fc5
2 touches
0 conflicts
0xe2263bea…6aa2
0x34ae4d…3fc5
2 touches
0 conflicts
0xf1a14809…56fd
0x34ae4d…3fc5
2 touches
0 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
1 conflict on slot 0x489114d737…75436d
Audit this contract →
← previous block·next block →recent activity