← previous blocknext block →recent activity
Analyzing
Block #83,400,313
41 transactions · 34 stateful · 2026-06-24 14:13:22 UTC
Parallelism
73/100
Blocked
68%
Avg conflicts / tx
1.9
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #83,400,313 · 41 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w18w29w310w411w513w626w627w928w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x757b0543…e087
0x34b655…2a6f
8 touches
6 conflicts
0x89fa3104…8020
0x34b655…2a6f
8 touches
6 conflicts
0x901d9f30…67a4
0x34b655…2a6f
8 touches
6 conflicts
0xa51c97e1…6b55
0x34b655…2a6f
8 touches
6 conflicts
0xe283e878…7262
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity