← previous blocknext block →recent activity
Analyzing
Block #103,213,509
26 transactions · 24 stateful · 2026-09-09 03:06:10 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,213,509 · 26 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
1w02w14w07w08w19w211w312w115w016w119w120w021w222w323w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x422d5490…52d9
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa977b13f…e8ba
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x4d42f16e…a6c9
0x1b6862…e19c
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
3 conflicts on slot 0x422d549061…1f52d9
Audit this contract →
← previous block·next block →recent activity