← previous blocknext block →recent activity
Analyzing
Block #103,049,347
22 transactions · 16 stateful · 2026-09-08 13:18:27 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,049,347 · 22 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
1w03w04w16w07w18w09w111w213w214w015w118w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe488f7b4…8be6
0x34b655…2a6f
10 touches
10 conflicts
0x81716ce9…095f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8be131d2…a340
0x34b655…2a6f
4 touches
1 conflict
0x9c6a9da2…c628
0x34b655…2a6f
4 touches
1 conflict
0xa35509fa…5cb3
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 0xe488f7b45c…038be6
Audit this contract →
← previous block·next block →recent activity