← previous blocknext block →recent activity
Analyzing
Block #103,212,924
11 transactions · 11 stateful · 2026-09-09 03:03:13 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,212,924 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w17w08w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae62d2a9…84dd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x4073f47e…39e6
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x9bff3222…a246
0x34b655…2a6f
2 touches
0 conflicts
0x9c088939…ddd7
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xae62d2a96c…2284dd
Audit this contract →
← previous block·next block →recent activity