← previous blocknext block →recent activity
Analyzing
Block #83,638,839
30 transactions · 30 stateful · 2026-06-25 16:45:25 UTC
Parallelism
53/100
Blocked
57%
Avg conflicts / tx
2.33
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,638,839 · 30 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
1w02w13w15w07w08w19w010w111w215w316w419w420w521w622w723w824w926w1127w1228w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xff4ee2c4…6e5e
0x34b655…2a6f
10 touches
10 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
10 touches
10 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
8 touches
6 conflicts
0x98e95e72…24dd
0x34b655…2a6f
6 touches
3 conflicts
0xa1e51cc8…e4cf
0x34b655…2a6f
6 touches
3 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity