← previous blocknext block →recent activity
Analyzing
Block #102,373,531
14 transactions · 14 stateful · 2026-09-06 04:24:52 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,373,531 · 14 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
2w03w04w15w29w310w411w512w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb682e7d…dde9
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
6 touches
3 conflicts
0x05989745…a42b
0x34b655…2a6f
4 touches
1 conflict
0x2c6ecedf…58f1
0x34b655…2a6f
4 touches
1 conflict
0x5f2e4654…3015
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0xfb682e7d8c…dcdde9
Audit this contract →
← previous block·next block →recent activity