← previous blocknext block →recent activity
Analyzing
Block #83,841,038
16 transactions · 9 stateful · 2026-06-26 15:14:31 UTC
Parallelism
88/100
Blocked
11%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,841,038 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0a7d825b…2b1e
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x30543e7c…957a
0x34b655…2a6f
2 touches
0 conflicts
0x44e13e21…432d
0x34b655…2a6f
2 touches
0 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
2 touches
0 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity