← previous blocknext block →recent activity
Analyzing
Block #83,625,160
29 transactions · 24 stateful · 2026-06-25 15:14:01 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,625,160 · 29 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
1w02w16w07w18w213w014w115w216w317w018w121w022w126w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xaa7ee7…f0e4
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c2
0x1b6862…e19c
4 touches
1 conflict
0xd364a7f3…7fc6
0x2a68ba…90c5
4 touches
1 conflict
0x0cdf9369…5331
0x34b655…2a6f
4 touches
1 conflict
0x3c9bce0e…0440
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity