← previous blocknext block →recent activity
Analyzing
Block #102,416,289
10 transactions · 9 stateful · 2026-09-06 08:01:32 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,416,289 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ca6fa7b…aeb3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5b6dd485…053b
0x34b655…2a6f
4 touches
1 conflict
0x0c78ade3…f11a
0x34b655…2a6f
2 touches
0 conflicts
0x1244b105…8e9b
0x34b655…2a6f
2 touches
0 conflicts
0xbcdd58ff…0711
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 0x9ca6fa7bcd…f2aeb3
Audit this contract →
← previous block·next block →recent activity