← previous blocknext block →recent activity
Analyzing
Block #102,860,852
19 transactions · 19 stateful · 2026-09-07 21:29:20 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,860,852 · 19 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
3w04w16w07w08w19w210w311w412w513w114w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
10 touches
10 conflicts
0x92216a75…77de
0x851145…3f07
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x032ec3de…2902
0x34b655…2a6f
5 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0x0edf889a…ce9d
0x01bff4…1071
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: 0x01bff417…bc1071
15 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity