← previous blocknext block →recent activity
Analyzing
Block #102,315,519
15 transactions · 15 stateful · 2026-09-05 23:31:00 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,315,519 · 15 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
1w02w04w15w16w27w08w110w311w412w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x65ff54af…aa01
0x34b655…2a6f
8 touches
6 conflicts
0x94e7f277…471b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x84f1799f…9466
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x17be1ca8…aca5
0x34b655…2a6f
4 touches
1 conflict
0x22f10271…841d
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity