← previous blocknext block →recent activity
Analyzing
Block #83,192,363
22 transactions · 17 stateful · 2026-06-23 15:04:03 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,192,363 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w19w114w215w316w417w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x042f82fe…3548
0x34b655…2a6f
6 touches
3 conflicts
0x2b2a4011…e869
0x34b655…2a6f
6 touches
3 conflicts
0x469e824a…d814
0x34b655…2a6f
6 touches
3 conflicts
0xa435dee8…f2be
0x34b655…2a6f
6 touches
3 conflicts
0x45e7e020…18aa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity