← previous blocknext block →recent activity
Analyzing
Block #102,307,699
20 transactions · 19 stateful · 2026-09-05 22:51:23 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,307,699 · 20 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
2w03w14w09w012w113w214w015w117w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x65ff54af…aa01
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x009b3c65…4334
0x34b655…2a6f
4 touches
1 conflict
0x01555e5f…b666
0x34b655…2a6f
4 touches
1 conflict
0xc1da8f73…484c
0x34b655…2a6f
4 touches
1 conflict
0x4d803b96…a832
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity