← previous blocknext block →recent activity
Analyzing
Block #83,584,430
17 transactions · 14 stateful · 2026-06-25 10:41:54 UTC
Parallelism
82/100
Blocked
43%
Avg conflicts / tx
0.59
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,584,430 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w08w111w215w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x901d9f30…67a4
0x34b655…2a6f
6 touches
3 conflicts
0x1ee4a6d2…6389
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x4979282b…2933
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x18904470…0ef9
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
3 conflicts on slot 0x901d9f3016…e767a4
Audit this contract →
← previous block·next block →recent activity