← previous blocknext block →recent activity
Analyzing
Block #103,215,823
23 transactions · 21 stateful · 2026-09-09 03:17:49 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #103,215,823 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w111w113w217w018w120w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf5192603…5640
0x34b655…2a6f
6 touches
3 conflicts
0x2c45dc1d…9eca
0x34b655…2a6f
6 touches
3 conflicts
0x36aa792c…a68d
0x34b655…2a6f
6 touches
3 conflicts
0x3a02129f…9eaf
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
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
15 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity