← previous blocknext block →recent activity
Analyzing
Block #102,043,997
19 transactions · 19 stateful · 2026-09-05 00:34:46 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,043,997 · 19 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
2w03w14w25w36w07w19w012w113w214w315w417w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x024b482b…16b0
0x34b655…2a6f
8 touches
6 conflicts
0x65f011a5…bc6e
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x9d7ac3b9…22f8
0x34b655…2a6f
8 touches
6 conflicts
0xa735de1d…29b0
0x34b655…2a6f
8 touches
6 conflicts
0xb826ef15…d248
0x34b655…2a6f
8 touches
6 conflicts
0xc4c059d8…185d
0x34b655…2a6f
8 touches
6 conflicts
0xdec2aeb2…0586
0x34b655…2a6f
8 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 0x024b482b0a…2616b0
Audit this contract →
← previous block·next block →recent activity