← previous blocknext block →recent activity
Analyzing
Block #102,524,785
24 transactions · 22 stateful · 2026-09-06 17:11:30 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.42
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #102,524,785 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w27w38w49w510w611w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x359866c7…de7b
0x34b655…2a6f
4 touches
1 conflict
0x37df7523…ccbb
0x754704…b603
2 touches
0 conflicts
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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity