← previous blocknext block →recent activity
Analyzing
Block #82,193,128
30 transactions · 24 stateful · 2026-06-18 23:48:02 UTC
Parallelism
87/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,193,128 · 30 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
1w02w13w04w06w18w111w114w015w119w020w121w025w127w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6767539b…f211
0x34b655…2a6f
6 touches
3 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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 0x6767539b91…9df211
Audit this contract →
← previous block·next block →recent activity