← previous blocknext block →recent activity
Analyzing
Block #100,109,665
17 transactions · 17 stateful · 2026-08-29 06:12:27 UTC
Parallelism
88/100
Blocked
24%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,109,665 · 17 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
1w02w19w010w011w113w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d9154e7…8821
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x41469894…5990
0x34b655…2a6f
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0x9965e5a3…44b3
0xd32edf…ff58
3 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
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 0x1d9154e7e4…148821
Audit this contract →
← previous block·next block →recent activity