← previous blocknext block →recent activity
Analyzing
Block #83,493,281
27 transactions · 23 stateful · 2026-06-25 00:34:06 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
1.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,493,281 · 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
3w04w16w29w010w111w212w313w414w515w618w523w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x6159d117…2e7e
0x34b655…2a6f
8 touches
6 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0x8d6cfd93…6eb6
0x34b655…2a6f
6 touches
3 conflicts
0xeb0b1d43…9559
0x34b655…2a6f
6 touches
3 conflicts
0x1c7763f6…89be
0x34b655…2a6f
4 touches
1 conflict
0x4b7ecbdb…6bc3
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity