← previous blocknext block →recent activity
Analyzing
Block #84,048,878
13 transactions · 11 stateful · 2026-06-27 14:19:45 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,048,878 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb5a511b…16e4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4418945a…98e0
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0xf33e4b5b…f860
0x34b655…2a6f
4 touches
1 conflict
0xf2db84ac…5503
0x34b655…2a6f
3 touches
1 conflict
0x1fd7f710…9437
0x34b655…2a6f
3 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
1 conflict on slot 0xfb5a511b23…9c16e4
Audit this contract →
← previous block·next block →recent activity