← previous blocknext block →recent activity
Analyzing
Block #83,661,705
16 transactions · 14 stateful · 2026-06-25 19:17:56 UTC
Parallelism
63/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,661,705 · 16 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
1w02w18w210w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x95cb8e34…5eba
0x34b655…2a6f
6 touches
3 conflicts
0x478e6e08…83bf
0x34b655…2a6f
4 touches
1 conflict
0x5abbda3b…0b02
0x34b655…2a6f
4 touches
1 conflict
0x98fc5672…13c7
0x34b655…2a6f
4 touches
1 conflict
0x9b58e20f…2dd9
0x34b655…2a6f
4 touches
1 conflict
0xbd5984ca…b2d6
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity