← previous blocknext block →recent activity
Analyzing
Block #102,741,120
30 transactions · 28 stateful · 2026-09-07 11:23:42 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,741,120 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w315w018w124w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x987859be…2686
0x34b655…2a6f
8 touches
6 conflicts
0x53e08444…d671
0x34b655…2a6f
8 touches
6 conflicts
0xd98afa6e…3364
0x34b655…2a6f
8 touches
6 conflicts
0x02372d42…1871
0x34b655…2a6f
8 touches
6 conflicts
0xdec2aeb2…0586
0x34b655…2a6f
6 touches
3 conflicts
0xacd90b9a…ea5c
0x34b655…2a6f
6 touches
3 conflicts
0x640cb6ed…6bfd
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
6 conflicts on slot 0x8bf661cb38…d4bcd2
Audit this contract →
← previous block·next block →recent activity