← previous blocknext block →recent activity
Analyzing
Block #83,656,252
14 transactions · 12 stateful · 2026-06-25 18:41:36 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,656,252 · 14 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
1w02w14w08w110w212w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f3fc680…f989
0x34b655…2a6f
6 touches
3 conflicts
0xcfe15fba…4f97
0x34b655…2a6f
6 touches
3 conflicts
0x8fcf2308…746e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x3f7ad3a0…de3b
0x34b655…2a6f
4 touches
1 conflict
0x540ae711…e092
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
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 0x5f3fc68024…49f989
Audit this contract →
← previous block·next block →recent activity