← previous blocknext block →recent activity
Analyzing
Block #84,248,611
15 transactions · 12 stateful · 2026-06-28 12:30:04 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,248,611 · 15 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
6w09w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x756ad195…36a3
0x34b655…2a6f
4 touches
1 conflict
0x93d680fb…ac21
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1f485a78…3dfe
0x34b655…2a6f
3 touches
1 conflict
0x24e133eb…b3c5
0x34b655…2a6f
3 touches
1 conflict
0xd8fd2add…50fc
0x69df8a…6292
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 0x756ad19507…7536a3
Audit this contract →
← previous block·next block →recent activity