← previous blocknext block →recent activity
Analyzing
Block #83,982,869
20 transactions · 17 stateful · 2026-06-27 07:00:02 UTC
Parallelism
85/100
Blocked
24%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,982,869 · 20 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
2w06w09w010w112w118w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x133163e2…48ca
0x34b655…2a6f
4 touches
1 conflict
0x1b2c54a1…5a76
0x34b655…2a6f
4 touches
1 conflict
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x41426688…9839
0x34b655…2a6f
4 touches
1 conflict
0x4467ecee…e95b
0x34b655…2a6f
4 touches
1 conflict
0x491501fe…d4db
0x34b655…2a6f
4 touches
1 conflict
0x5d2267cd…440e
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
1 conflict on slot 0x133163e291…5048ca
Audit this contract →
← previous block·next block →recent activity