← previous blocknext block →recent activity
Analyzing
Block #83,966,151
16 transactions · 14 stateful · 2026-06-27 05:08:36 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,966,151 · 16 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
1w04w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x01e7b865…6e70
0x188d58…ea8e
4 touches
1 conflict
0x5d601a99…43f6
0x188d58…ea8e
4 touches
1 conflict
0x5d601a99…43f7
0x188d58…ea8e
4 touches
1 conflict
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
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 0x8e5cc69035…0db06b
Audit this contract →
← previous block·next block →recent activity