← previous blocknext block →recent activity
Analyzing
Block #100,726,873
17 transactions · 16 stateful · 2026-08-31 10:01:54 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,726,873 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w18w211w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27b6010e…e4aa
0x34b655…2a6f
6 touches
3 conflicts
0xdbdf75c2…e98a
0x34b655…2a6f
4 touches
1 conflict
0x0dd35cde…b69b
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x68531239…e9a3
0x34b655…2a6f
4 touches
1 conflict
0x9482a067…eba9
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
3 conflicts on slot 0x27b6010e94…34e4aa
Audit this contract →
← previous block·next block →recent activity