← previous blocknext block →recent activity
Analyzing
Block #103,050,477
26 transactions · 26 stateful · 2026-09-08 13:24:08 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #103,050,477 · 26 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
2w03w16w27w08w19w313w417w419w020w125w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc9f022e…a01c
0x34b655…2a6f
8 touches
6 conflicts
0x25180879…8191
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xb30f077a…1c26
0x34b655…2a6f
6 touches
3 conflicts
0x17bbe4f8…08c5
0xe52b14…7230
4 touches
1 conflict
0x3cebc8f1…975c
0xe52b14…7230
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
6 conflicts on slot 0xfc9f022e89…3da01c
Audit this contract →
← previous block·next block →recent activity