← previous blocknext block →recent activity
Analyzing
Block #102,063,950
24 transactions · 22 stateful · 2026-09-05 02:15:53 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,063,950 · 24 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
1w02w14w05w16w27w312w013w115w017w121w022w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01315072…0e2d
0x34b655…2a6f
8 touches
6 conflicts
0xeb4304a5…dd06
0x34b655…2a6f
8 touches
6 conflicts
0xd98afa6e…3364
0x34b655…2a6f
8 touches
6 conflicts
0x987859be…2686
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x79ec4509…1f61
0x34b655…2a6f
8 touches
6 conflicts
0xf5d28bce…c32c
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 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 0x013150720a…500e2d
Audit this contract →
← previous block·next block →recent activity