← previous blocknext block →recent activity
Analyzing
Block #84,083,103
17 transactions · 13 stateful · 2026-06-27 18:07:42 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,083,103 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w28w112w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc54eb34…fe58
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x19ce481d…6c36
0x34b655…2a6f
4 touches
1 conflict
0x1ad22eda…4802
0x34b655…2a6f
4 touches
1 conflict
0x1c1e591b…d93d
0x34b655…2a6f
4 touches
1 conflict
0x32359294…7113
0x34b655…2a6f
4 touches
1 conflict
0x76d9c305…97e8
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 0xdc54eb34c4…49fe58
Audit this contract →
← previous block·next block →recent activity