← previous blocknext block →recent activity
Analyzing
Block #83,844,159
16 transactions · 14 stateful · 2026-06-26 15:35:22 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,844,159 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w312w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x365c0935…6c20
0x34b655…2a6f
6 touches
3 conflicts
0x7cb1d883…dc23
0x34b655…2a6f
6 touches
3 conflicts
0xd01910c9…9418
0x34b655…2a6f
6 touches
3 conflicts
0xd58b9a66…1c23
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x5ad1e512…4740
0x34b655…2a6f
6 touches
3 conflicts
0x120847e2…98c2
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
3 conflicts on slot 0x365c093515…3c6c20
Audit this contract →
← previous block·next block →recent activity