← previous blocknext block →recent activity
Analyzing
Block #102,140,129
27 transactions · 25 stateful · 2026-09-05 08:42:12 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,140,129 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w28w09w111w016w117w218w320w421w022w123w225w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a3ba206…5fe0
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
6 touches
3 conflicts
0x9210e826…1414
0x34b655…2a6f
6 touches
3 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x7a3ba20696…9a5fe0
Audit this contract →
← previous block·next block →recent activity