← previous blocknext block →recent activity
Analyzing
Block #100,734,011
21 transactions · 17 stateful · 2026-08-31 10:37:48 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,734,011 · 21 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
1w02w03w010w111w012w013w014w115w216w117w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8311570f…5321
0x34b655…2a6f
6 touches
3 conflicts
0x79347b24…9fba
0x34b655…2a6f
6 touches
3 conflicts
0x050e446f…873f
0x34b655…2a6f
4 touches
1 conflict
0x3b923ba9…0a8f
0x34b655…2a6f
4 touches
1 conflict
0x587c3223…8560
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xb26ff3de…9352
0xa6afd3…d132
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity