← previous blocknext block →recent activity
Analyzing
Block #83,935,653
15 transactions · 15 stateful · 2026-06-27 01:45:22 UTC
Parallelism
87/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,935,653 · 15 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
1w02w111w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9f405549…5e9c
0x34b655…2a6f
3 touches
1 conflict
0x7899e9bf…8449
0x34b655…2a6f
3 touches
1 conflict
0x94a63bef…f7c1
0x40c49f…2af0
2 touches
0 conflicts
0x98ff6308…8200
0x40c49f…2af0
2 touches
0 conflicts
0xc6d1e11f…4bbc
0x40c49f…2af0
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 0xafd867b7ed…d92b2d
Audit this contract →
← previous block·next block →recent activity