← previous blocknext block →recent activity
Analyzing
Block #102,519,007
17 transactions · 17 stateful · 2026-09-06 16:42:10 UTC
Parallelism
82/100
Blocked
24%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,519,007 · 17 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
1w02w13w213w014w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2c7e330…9e6a
0x34b655…2a6f
6 touches
3 conflicts
0x0d19cd25…a3c2
0x34b655…2a6f
4 touches
1 conflict
0x176d125e…2608
0x34b655…2a6f
4 touches
1 conflict
0x21adef83…f2b7
0x34b655…2a6f
4 touches
1 conflict
0x23d03847…102d
0x34b655…2a6f
4 touches
1 conflict
0x3027f5b0…7a3f
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x4dffc33e…068d
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 0xe2c7e33010…df9e6a
Audit this contract →
← previous block·next block →recent activity