← previous blocknext block →recent activity
Analyzing
Block #83,968,188
13 transactions · 11 stateful · 2026-06-27 05:22:12 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,968,188 · 13 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
1w08w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b7af531…48f1
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3eef5e65…6eb0
0x34b655…2a6f
2 touches
0 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0x7e546ac5…b453
0x34b655…2a6f
2 touches
0 conflicts
0x860cda0b…b1b7
0x34b655…2a6f
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0x7b7af53137…5748f1
Audit this contract →
← previous block·next block →recent activity