← previous blocknext block →recent activity
Analyzing
Block #100,585,787
21 transactions · 18 stateful · 2026-08-30 22:12:11 UTC
Parallelism
90/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,585,787 · 21 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
5w012w014w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeadd5eb8…335a
0x34b655…2a6f
4 touches
1 conflict
0xebd39fb2…1c34
0x34b655…2a6f
4 touches
1 conflict
0x0b3eb43a…ca08
0x34b655…2a6f
4 touches
1 conflict
0x9ca6fa7b…aeb3
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0xab94749e…6100
0x1c8a33…d316
2 touches
0 conflicts
0xd3bbdd6b…665b
0x1c8a33…d316
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0xeadd5eb8bf…42335a
Audit this contract →
← previous block·next block →recent activity