← previous blocknext block →recent activity
Analyzing
Block #84,241,410
12 transactions · 10 stateful · 2026-06-28 11:42:09 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,241,410 · 12 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
9w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0xa1571d54…ae41
0x34b655…2a6f
4 touches
1 conflict
0x014ab7d0…5148
0x2ab50b…5c41
2 touches
0 conflicts
0x0d5b04cc…fe5f
0x2ab50b…5c41
2 touches
0 conflicts
0x11b3ac40…fbcf
0x2ab50b…5c41
2 touches
0 conflicts
0x16f4fddd…ed82
0x2ab50b…5c41
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
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 0x7ee6007b44…92fd68
Audit this contract →
← previous block·next block →recent activity