← previous blocknext block →recent activity
Analyzing
Block #83,654,318
17 transactions · 17 stateful · 2026-06-25 18:28:45 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,654,318 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w011w112w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79e62da8…efdc
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0x7dc64b2c…05e7
0x34b655…2a6f
4 touches
1 conflict
0xdb7c435f…f490
0x34b655…2a6f
3 touches
1 conflict
0x57179420…128a
0x34b655…2a6f
2 touches
0 conflicts
0x5d7f309d…5145
0x34b655…2a6f
2 touches
0 conflicts
0x68d9eb83…2cc7
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 0x79e62da89b…71efdc
Audit this contract →
← previous block·next block →recent activity