← previous blocknext block →recent activity
Analyzing
Block #100,727,115
16 transactions · 16 stateful · 2026-08-31 10:03:07 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,727,115 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w16w27w38w211w212w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x27b6010e…e4aa
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xe4da214b…c9a4
0x34b655…2a6f
4 touches
1 conflict
0x211f919a…7a71
0x34b655…2a6f
4 touches
1 conflict
0xc6503c74…fb96
0x34b655…2a6f
4 touches
1 conflict
0x68ec1d3b…cba0
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity