← previous blocknext block →recent activity
Analyzing
Block #102,283,465
18 transactions · 18 stateful · 2026-09-05 20:48:42 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,283,465 · 18 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
2w03w14w25w06w17w38w416w017w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x9bff3222…a246
0x34b655…2a6f
8 touches
6 conflicts
0xae8a7697…9685
0x34b655…2a6f
8 touches
6 conflicts
0xc9ca92b3…ac3f
0x34b655…2a6f
8 touches
6 conflicts
0xf5d28bce…c32c
0x34b655…2a6f
8 touches
6 conflicts
0x5f749304…d1c1
0x34b655…2a6f
7 touches
6 conflicts
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 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity