← previous blocknext block →recent activity
Analyzing
Block #83,655,240
16 transactions · 13 stateful · 2026-06-25 18:34:51 UTC
Parallelism
75/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,655,240 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x478e6e08…83bf
0x34b655…2a6f
4 touches
1 conflict
0xd064a456…b881
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x16dce2e7…6f05
0x34b655…2a6f
4 touches
1 conflict
0x729c91b8…9539
0x188d58…ea8e
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x0a8f8b9c…3046
0x34b655…2a6f
2 touches
0 conflicts
0x11622504…ed25
0x754704…b603
2 touches
0 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
1 conflict on slot 0x478e6e0871…8083bf
Audit this contract →
← previous block·next block →recent activity