← previous blocknext block →recent activity
Analyzing
Block #83,979,910
23 transactions · 21 stateful · 2026-06-27 06:40:17 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,979,910 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w09w010w113w017w119w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
4 touches
1 conflict
0xe75ce681…ba60
0x188d58…ea8e
4 touches
1 conflict
0x0dbf9688…c6cf
0xd18b7e…414b
4 touches
1 conflict
0x785889c9…0603
0x34b655…2a6f
4 touches
1 conflict
0xb670a63e…ead8
0x34b655…2a6f
4 touches
1 conflict
0xde696e46…6446
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity