← previous blocknext block →recent activity
Analyzing
Block #100,063,093
18 transactions · 17 stateful · 2026-08-29 02:17:58 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,063,093 · 18 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
3w06w08w09w111w212w313w414w516w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb673caa…300e
0x34b655…2a6f
10 touches
10 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
8 touches
6 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0x916a1238…6258
0x34b655…2a6f
6 touches
3 conflicts
0x24bb46f7…3853
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0xbec85ae9…adc4
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
10 conflicts on slot 0xbb673caac8…8f300e
Audit this contract →
← previous block·next block →recent activity