← previous blocknext block →recent activity
Analyzing
Block #83,402,121
24 transactions · 18 stateful · 2026-06-24 14:25:26 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,402,121 · 24 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
1w02w13w14w25w06w17w28w39w013w221w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
6 touches
3 conflicts
0x0835adb5…ad83
0x34b655…2a6f
6 touches
3 conflicts
0x67fa0d46…3c8e
0xa6afd3…d132
5 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xd1480c90…ae0a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity