← previous blocknext block →recent activity
Analyzing
Block #84,130,326
20 transactions · 18 stateful · 2026-06-27 23:22:25 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,130,326 · 20 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
1w02w18w09w110w014w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50b7ca2f…a506
0x34b655…2a6f
6 touches
3 conflicts
0x5a30d8a9…f768
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x1d30b594…5823
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x607849f0…e3cc
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 0x50b7ca2f7a…17a506
Audit this contract →
← previous block·next block →recent activity