← previous blocknext block →recent activity
Analyzing
Block #83,483,127
10 transactions · 8 stateful · 2026-06-24 23:26:24 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,483,127 · 10 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
3w04w15w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb99958f6…ccf1
0x34b655…2a6f
4 touches
1 conflict
0x1c7763f6…89be
0x34b655…2a6f
4 touches
1 conflict
0x18ca6535…87c1
0x34b655…2a6f
4 touches
1 conflict
0x709c5c4c…bd35
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb99958f6…ccf0
0x34b655…2a6f
4 touches
1 conflict
0x5dc2541c…dd2f
0x34b655…2a6f
3 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
1 conflict on slot 0xb99958f6c8…c6ccf1
Audit this contract →
← previous block·next block →recent activity