← previous blocknext block →recent activity
Analyzing
Block #100,268,431
14 transactions · 14 stateful · 2026-08-29 19:33:17 UTC
Parallelism
64/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,268,431 · 14 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
1w04w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23529e13…6f25
0x34b655…2a6f
4 touches
1 conflict
0x4786839b…c29a
0x34b655…2a6f
4 touches
1 conflict
0x2827ae77…4368
0x34b655…2a6f
4 touches
1 conflict
0x5e4ed8fb…2d93
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
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 0x23529e136b…8a6f25
Audit this contract →
← previous block·next block →recent activity