← previous blocknext block →recent activity
Analyzing
Block #100,140,276
42 transactions · 23 stateful · 2026-08-29 08:46:43 UTC
Parallelism
93/100
Blocked
35%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,140,276 · 42 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
1w02w14w06w011w112w024w127w133w234w135w239w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x4279296f…2983
0x34b655…2a6f
4 touches
1 conflict
0x4e44fd40…7335
0x34b655…2a6f
4 touches
1 conflict
0x6527b0cd…3c03
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 0x676f9f01ee…dea8ac
Audit this contract →
← previous block·next block →recent activity