← previous blocknext block →recent activity
Analyzing
Block #100,226,763
18 transactions · 16 stateful · 2026-08-29 16:02:05 UTC
Parallelism
72/100
Blocked
25%
Avg conflicts / tx
0.28
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,226,763 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w113w214w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bdffe1c…2a9e
0x34b655…2a6f
6 touches
3 conflicts
0x27b6010e…e4aa
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x189853b5…250d
0x34b655…2a6f
2 touches
0 conflicts
0x1f77ce8f…f484
0x34b655…2a6f
2 touches
0 conflicts
0x275b0236…82ec
0x34b655…2a6f
2 touches
0 conflicts
0x45f2035a…1803
0x34b655…2a6f
2 touches
0 conflicts
0x48e8d6ad…8675
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 0x5bdffe1ce5…c42a9e
Audit this contract →
← previous block·next block →recent activity