← previous blocknext block →recent activity
Analyzing
Block #103,215,675
21 transactions · 20 stateful · 2026-09-09 03:17:05 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,215,675 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w27w39w410w515w416w519w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71549b2e…6bc3
0x34b655…2a6f
8 touches
6 conflicts
0xd7443f37…eb79
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1d2440dc…12d6
0x34b655…2a6f
4 touches
1 conflict
0x754bbcbe…427e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
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 0x71549b2e34…7c6bc3
Audit this contract →
← previous block·next block →recent activity