← previous blocknext block →recent activity
Analyzing
Block #83,642,248
27 transactions · 24 stateful · 2026-06-25 17:08:11 UTC
Parallelism
70/100
Blocked
46%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,642,248 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w27w310w011w115w016w217w318w419w520w621w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee7978e9…2869
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x7fe97198…79ab
0x34b655…2a6f
8 touches
6 conflicts
0x3a53ab79…6fef
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x6291bb10…5dc3
0x34b655…2a6f
4 touches
1 conflict
0x7e6c970a…65af
0x34b655…2a6f
4 touches
1 conflict
0x8802094b…3402
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
10 conflicts on slot 0xee7978e97a…ed2869
Audit this contract →
← previous block·next block →recent activity