← previous blocknext block →recent activity
Analyzing
Block #83,410,573
22 transactions · 20 stateful · 2026-06-24 15:21:57 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,410,573 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w08w19w110w211w313w014w117w219w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b9800d…0682
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x757b0543…e087
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x23fd1977…6b5e
0x34b655…2a6f
6 touches
3 conflicts
0xec7b070f…db9a
0x34b655…2a6f
6 touches
3 conflicts
0xdb067026…9eb8
0x69df8a…6292
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 0xb6b9800ded…2b0682
Audit this contract →
← previous block·next block →recent activity