← previous blocknext block →recent activity
Analyzing
Block #100,612,474
25 transactions · 21 stateful · 2026-08-31 00:26:27 UTC
Parallelism
84/100
Blocked
24%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,612,474 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w012w013w117w220w323w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xe2de1aea…8024
0x34b655…2a6f
8 touches
6 conflicts
0x75e8ccd6…b9de
0x34b655…2a6f
6 touches
3 conflicts
0x6a121dee…18bc
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xf65c9ad4…88f7
0x34b655…2a6f
4 touches
1 conflict
0x00f19757…9252
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
6 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity