← previous blocknext block →recent activity
Analyzing
Block #102,307,558
14 transactions · 14 stateful · 2026-09-05 22:50:39 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,307,558 · 14 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
1w02w13w04w15w26w29w210w311w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf025f81…a7c4
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x65ff54af…aa01
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x0f94ee4c…1898
0x1b6862…e19c
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
3 conflicts on slot 0xdf025f810d…4fa7c4
Audit this contract →
← previous block·next block →recent activity