← previous blocknext block →recent activity
Analyzing
Block #83,695,112
22 transactions · 21 stateful · 2026-06-25 23:00:50 UTC
Parallelism
91/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,695,112 · 22 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w114w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0xfbabb02d…af07
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x7c403af1…31b1
0x3bd359…433a
2 touches
0 conflicts
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 0x3fa1fac42c…ba826c
Audit this contract →
← previous block·next block →recent activity