← previous blocknext block →recent activity
Analyzing
Block #100,154,881
13 transactions · 9 stateful · 2026-08-29 10:00:15 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,154,881 · 13 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
1w07w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe27b7f98…8e64
0x34b655…2a6f
4 touches
1 conflict
0x1e168c8b…6945
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x9d6a99f9…da64
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xd8917529…9e59
0x34b655…2a6f
4 touches
1 conflict
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 0xe27b7f98f5…498e64
Audit this contract →
← previous block·next block →recent activity