← previous blocknext block →recent activity
Analyzing
Block #102,407,083
41 transactions · 23 stateful · 2026-09-06 07:14:53 UTC
Parallelism
90/100
Blocked
39%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,407,083 · 41 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w08w19w114w017w018w122w129w030w131w232w333w134w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbca708a…981e
0x34b655…2a6f
8 touches
6 conflicts
0xc852b267…9d14
0x34b655…2a6f
8 touches
6 conflicts
0x25957369…c648
0x34b655…2a6f
6 touches
3 conflicts
0x46fa0295…e1db
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0xbbca708a63…a4981e
Audit this contract →
← previous block·next block →recent activity