← previous blocknext block →recent activity
Analyzing
Block #101,672,103
28 transactions · 25 stateful · 2026-09-03 17:18:02 UTC
Parallelism
79/100
Blocked
24%
Avg conflicts / tx
0.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,672,103 · 28 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
1w04w17w28w39w411w226w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x5aca92a2…b218
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x9ba10aad…9bc5
0x34b655…2a6f
4 touches
1 conflict
0x0b7b942e…f3f4
0x34b655…2a6f
2 touches
0 conflicts
0x0fc7f5a7…6b22
0x34b655…2a6f
2 touches
0 conflicts
0x123a68b3…202a
0x34b655…2a6f
2 touches
0 conflicts
0x23d6de6f…da9c
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity