← previous blocknext block →recent activity
Analyzing
Block #83,653,454
16 transactions · 13 stateful · 2026-06-25 18:23:00 UTC
Parallelism
75/100
Blocked
54%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,653,454 · 16 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
1w03w14w25w06w17w28w311w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d64bba6…c643
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0x925c118c…a1d8
0x34b655…2a6f
6 touches
3 conflicts
0x75bd64f6…cc40
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
0x939a5d3a…3c36
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 0x0d64bba671…53c643
Audit this contract →
← previous block·next block →recent activity