← previous blocknext block →recent activity
Analyzing
Block #100,432,253
10 transactions · 10 stateful · 2026-08-30 09:19:43 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,432,253 · 10 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09bd1e16…1992
0x34b655…2a6f
4 touches
1 conflict
0xf61165ef…adb9
0x34b655…2a6f
4 touches
1 conflict
0xfeac3ee8…6570
0x34b655…2a6f
4 touches
1 conflict
0x97420b44…a2a8
0x34b655…2a6f
4 touches
1 conflict
0xab3ad3dc…2a56
0x34b655…2a6f
2 touches
0 conflicts
0xbd3735d7…c973
0x34b655…2a6f
2 touches
0 conflicts
0xe2d50773…c39e
0x34b655…2a6f
2 touches
0 conflicts
0x437393f5…3a8f
0x3bd359…433a
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 0x09bd1e16a9…681992
Audit this contract →
← previous block·next block →recent activity