← previous blocknext block →recent activity
Analyzing
Block #83,409,927
19 transactions · 19 stateful · 2026-06-24 15:17:38 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,409,927 · 19 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
1w02w13w04w05w06w17w08w19w212w014w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb13034e…be94
0x34b655…2a6f
6 touches
3 conflicts
0x4efb974a…6126
0x34b655…2a6f
4 touches
2 conflicts
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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 0xdb13034e34…eabe94
Audit this contract →
← previous block·next block →recent activity