← previous blocknext block →recent activity
Analyzing
Block #83,691,755
16 transactions · 16 stateful · 2026-06-25 22:38:24 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,691,755 · 16 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
2w03w14w27w08w010w111w113w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x206fb8db…a146
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
6 touches
3 conflicts
0x3a20350d…e8e6
0x34b655…2a6f
4 touches
1 conflict
0x34786594…61d6
0x34b655…2a6f
4 touches
1 conflict
0x864353d4…dcb7
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 0x206fb8db95…b8a146
Audit this contract →
← previous block·next block →recent activity