← previous blocknext block →recent activity
Analyzing
Block #102,480,228
15 transactions · 15 stateful · 2026-09-06 13:25:27 UTC
Parallelism
40/100
Blocked
53%
Avg conflicts / tx
2.13
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #102,480,228 · 15 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w18w29w310w411w512w613w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x886db264…846e
0x34b655…2a6f
10 touches
10 conflicts
0x184a9b09…c825
0x34b655…2a6f
8 touches
6 conflicts
0x4d1d85aa…01a0
0x34b655…2a6f
7 touches
6 conflicts
0x86765f19…8ec6
0x34b655…2a6f
4 touches
1 conflict
0x13938a09…5f88
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity