← previous blocknext block →recent activity
Analyzing
Block #83,665,735
12 transactions · 11 stateful · 2026-06-25 19:44:48 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,665,735 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52ff776e…b7db
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0xd379a368…fea4
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x1c48b3ac…a03c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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
1 conflict on slot 0x52ff776eb1…12b7db
Audit this contract →
← previous block·next block →recent activity