← previous blocknext block →recent activity
Analyzing
Block #103,222,308
14 transactions · 13 stateful · 2026-09-09 03:50:30 UTC
Parallelism
79/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,222,308 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a9e408e…3721
0x34b655…2a6f
4 touches
1 conflict
0x75f928fc…0465
0x34b655…2a6f
4 touches
1 conflict
0x76bb94df…daf6
0x34b655…2a6f
4 touches
1 conflict
0xb6aedce9…a483
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0990ecee…b4f1
0x34b655…2a6f
2 touches
0 conflicts
0x0f13b598…f75b
0x34b655…2a6f
2 touches
0 conflicts
0x0f763490…ff64
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 0x6a9e408e97…fb3721
Audit this contract →
← previous block·next block →recent activity