← previous blocknext block →recent activity
Analyzing
Block #102,223,322
34 transactions · 32 stateful · 2026-09-05 15:43:44 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,223,322 · 34 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
1w07w09w110w016w117w218w320w021w122w425w130w032w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xdd6cf50f…e383
0x34b655…2a6f
6 touches
3 conflicts
0xcb06d6a1…b04f
0x34b655…2a6f
6 touches
3 conflicts
0x2c539d94…b63a
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
0x34b655…2a6f
5 touches
3 conflicts
0xadaf0a0f…5a85
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
6 conflicts on slot 0xc824469a90…af641f
Audit this contract →
← previous block·next block →recent activity