← previous blocknext block →recent activity
Analyzing
Block #100,617,187
20 transactions · 18 stateful · 2026-08-31 00:50:09 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,617,187 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w113w217w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2de1aea…8024
0x34b655…2a6f
6 touches
3 conflicts
0x948c6523…a18b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x107b89e4…470d
0x34b655…2a6f
2 touches
0 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
2 touches
0 conflicts
0x51e605f9…b7ac
0x34b655…2a6f
2 touches
0 conflicts
0x5e917f4c…9730
0x34b655…2a6f
2 touches
0 conflicts
0x7867ad58…cf21
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
3 conflicts on slot 0xe2de1aeae5…be8024
Audit this contract →
← previous block·next block →recent activity