← previous blocknext block →recent activity
Analyzing
Block #102,247,150
18 transactions · 17 stateful · 2026-09-05 17:44:34 UTC
Parallelism
61/100
Blocked
59%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,247,150 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w29w010w111w213w314w415w516w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5da92df7…74b5
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf20c6ffa…b478
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x06afe596…21f2
0x34b655…2a6f
6 touches
3 conflicts
0x2f5b82cb…9bd1
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
10 conflicts on slot 0x5da92df7bf…9274b5
Audit this contract →
← previous block·next block →recent activity