← previous blocknext block →recent activity
Analyzing
Block #83,455,391
13 transactions · 10 stateful · 2026-06-24 20:21:19 UTC
Parallelism
69/100
Blocked
30%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,455,391 · 13 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
5w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6ca8bab1…3957
0x34b655…2a6f
4 touches
1 conflict
0xbe96a4fc…e499
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x4af1f048…73fe
0x065c9d…c394
2 touches
0 conflicts
0x66e9c3d6…e53c
0x065c9d…c394
2 touches
0 conflicts
0xb8834321…5c31
0x065c9d…c394
2 touches
0 conflicts
0xc3352dca…601c
0x065c9d…c394
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity