← previous blocknext block →recent activity
Analyzing
Block #102,737,038
23 transactions · 23 stateful · 2026-09-07 11:03:10 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.22
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,737,038 · 23 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
1w02w110w012w114w019w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0x73bb65fc…650d
0x754704…b603
4 touches
1 conflict
0xc98b6062…73eb
0x754704…b603
4 touches
1 conflict
0xd1eae902…bfd4
0x754704…b603
4 touches
1 conflict
0x14b2b355…8ce5
0x99c7a7…8bf0
4 touches
1 conflict
0xc446711e…b7cb
0x99c7a7…8bf0
4 touches
1 conflict
0x167de262…f61f
0x34b655…2a6f
4 touches
1 conflict
0x6fce7a05…d778
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
1 conflict on slot 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity