← previous blocknext block →recent activity
Analyzing
Block #100,266,156
17 transactions · 13 stateful · 2026-08-29 19:21:41 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,266,156 · 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
3w07w09w111w013w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f90c530…dd82
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x8b780b26…f5ff
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1032f16c…a9b1
0x34b655…2a6f
2 touches
0 conflicts
0x1faeed20…190f
0x34b655…2a6f
2 touches
0 conflicts
0x1fb8364c…c10d
0x34b655…2a6f
2 touches
0 conflicts
0x3c9b10c1…d791
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
1 conflict on slot 0x1f90c5303a…ecdd82
Audit this contract →
← previous block·next block →recent activity