← previous blocknext block →recent activity
Analyzing
Block #103,222,423
20 transactions · 19 stateful · 2026-09-09 03:51:05 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,222,423 · 20 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
1w02w15w26w313w314w415w016w117w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x7c68d10b…8386
0x34b655…2a6f
8 touches
6 conflicts
0xfa09be5a…1e79
0x34b655…2a6f
6 touches
3 conflicts
0xbfb4b02a…4b47
0x34b655…2a6f
4 touches
1 conflict
0xc323846a…f921
0x34b655…2a6f
4 touches
1 conflict
0xfee9c1d5…61d6
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity