← previous blocknext block →recent activity
Analyzing
Block #102,011,936
16 transactions · 16 stateful · 2026-09-04 21:52:30 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,011,936 · 16 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
2w03w14w05w07w08w19w210w312w213w114w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x75a77817…b0ed
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8a6af6a7…5f10
0x34b655…2a6f
4 touches
1 conflict
0x37df7523…ccbb
0x754704…b603
4 touches
1 conflict
0xb652da8f…1216
0x754704…b603
4 touches
1 conflict
0xf96d61f8…8fd8
0x754704…b603
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity