← previous blocknext block →recent activity
Analyzing
Block #102,273,350
17 transactions · 15 stateful · 2026-09-05 19:57:20 UTC
Parallelism
59/100
Blocked
40%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,273,350 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w210w311w412w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x65ff54af…aa01
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x4854b070…fb81
0x34b655…2a6f
5 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
5 touches
3 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity