← previous blocknext block →recent activity
Analyzing
Block #84,306,738
15 transactions · 14 stateful · 2026-06-28 18:57:23 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,306,738 · 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
1w05w06w17w08w19w111w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5970b31…f34c
0x34b655…2a6f
6 touches
3 conflicts
0x7dc64b2c…05e7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1b06c33a…7561
0x34b655…2a6f
6 touches
3 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0x80f17de3…8334
0x34b655…2a6f
4 touches
1 conflict
0x892eedd0…bf40
0x34b655…2a6f
4 touches
1 conflict
0xb1993ff2…a1cf
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 0xf5970b3144…10f34c
Audit this contract →
← previous block·next block →recent activity