← previous blocknext block →recent activity
Analyzing
Block #100,787,675
18 transactions · 16 stateful · 2026-08-31 15:07:55 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,787,675 · 18 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
5w08w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76622fb2…4f08
0x34b655…2a6f
4 touches
1 conflict
0x81716ce9…095f
0x34b655…2a6f
4 touches
1 conflict
0x0217a039…5d4c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3a3e7727…36c5
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…1868
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…186c
0x34ae4d…3fc5
2 touches
0 conflicts
0x6cd67eff…f738
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 0x76622fb2e3…024f08
Audit this contract →
← previous block·next block →recent activity