← previous blocknext block →recent activity
Analyzing
Block #83,671,857
16 transactions · 15 stateful · 2026-06-25 20:25:39 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,671,857 · 16 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
1w06w07w19w110w011w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f4dc602…5a18
0x34b655…2a6f
6 touches
3 conflicts
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1e346a85…e9c5
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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
3 conflicts on slot 0x3f4dc6022b…0e5a18
Audit this contract →
← previous block·next block →recent activity