← previous blocknext block →recent activity
Analyzing
Block #101,802,903
19 transactions · 17 stateful · 2026-09-04 04:15:55 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,802,903 · 19 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
1w02w03w16w27w313w315w416w517w118w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc8fb280…76a3
0x34b655…2a6f
8 touches
6 conflicts
0xf4497fd3…6ff0
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0x6324ccc9…14fd
0x34b655…2a6f
6 touches
3 conflicts
0x6f58eb90…7686
0x34b655…2a6f
6 touches
3 conflicts
0xada087b9…4aca
0x34b655…2a6f
6 touches
3 conflicts
0xbd590df7…9891
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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 0xbc8fb28081…2176a3
Audit this contract →
← previous block·next block →recent activity