← previous blocknext block →recent activity
Analyzing
Block #102,212,566
20 transactions · 18 stateful · 2026-09-05 14:49:25 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,212,566 · 20 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
1w02w14w06w17w012w113w214w315w417w018w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a6f5e37…6c3c
0x34b655…2a6f
10 touches
10 conflicts
0x56a284d9…32e4
0x34b655…2a6f
8 touches
6 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x01a720cc…00d5
0x34b655…2a6f
7 touches
6 conflicts
0xaeafdc4c…b966
0x34b655…2a6f
7 touches
6 conflicts
0xf84115d7…2d22
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 0x0a6f5e3795…116c3c
Audit this contract →
← previous block·next block →recent activity