← previous blocknext block →recent activity
Analyzing
Block #83,668,473
48 transactions · 34 stateful · 2026-06-25 20:03:06 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1.69
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,668,473 · 48 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w28w016w017w119w020w124w225w326w427w528w629w730w832w1033w1134w1237w138w341w443w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
22 touches
55 conflicts
0x65df2980…8edc
0x34b655…2a6f
12 touches
15 conflicts
0xd4702f73…926c
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x75cdffd8…c217
0x34b655…2a6f
10 touches
10 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
10 touches
10 conflicts
0x864353d4…dcb7
0x34b655…2a6f
10 touches
10 conflicts
0x5b91dc39…d097
0x34b655…2a6f
10 touches
10 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
55 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity