← previous blocknext block →recent activity
Analyzing
Block #102,013,747
23 transactions · 23 stateful · 2026-09-04 22:01:39 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,013,747 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w08w09w010w011w112w213w115w216w119w321w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x8881a9a9…b1ac
0x99c7a7…8bf0
4 touches
1 conflict
0x32070dd0…692b
0x754704…b603
4 touches
1 conflict
0x5cb99fee…00cf
0x754704…b603
4 touches
1 conflict
0xde93ff88…37ec
0x754704…b603
4 touches
1 conflict
0x3dbaed38…1c8a
0x99c7a7…8bf0
4 touches
1 conflict
0x20b94f7c…2a9b
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity