← previous blocknext block →recent activity
Analyzing
Block #83,493,272
15 transactions · 15 stateful · 2026-06-25 00:34:02 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,493,272 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w18w19w212w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfd77e6c1…264b
0x34b655…2a6f
4 touches
1 conflict
0xd2453506…54e4
0x34b655…2a6f
4 touches
1 conflict
0xdc86f14d…f80d
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xfd5ef2cf…02ae
0x34b655…2a6f
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x05289bd6…9ab4
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity