← previous blocknext block →recent activity
Analyzing
Block #100,161,854
10 transactions · 9 stateful · 2026-08-29 10:35:21 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,161,854 · 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
3w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03fe6234…08dd
0x34b655…2a6f
4 touches
1 conflict
0x03fe6234…08de
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0ad69505…af82
0x34b655…2a6f
2 touches
0 conflicts
0x1bee5aea…5f61
0x34b655…2a6f
2 touches
0 conflicts
0x2ad2f4bc…1800
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8dee
0x34b655…2a6f
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 0x03fe62345d…1808dd
Audit this contract →
← previous block·next block →recent activity