← previous blocknext block →recent activity
Analyzing
Block #84,315,147
44 transactions · 40 stateful · 2026-06-28 19:53:19 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
1.82
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #84,315,147 · 44 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w014w215w016w117w218w319w021w122w223w124w225w230w331w432w335w336w437w538w639w743w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xf4b4898d…f948
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x1d4b0baf…1423
0x34b655…2a6f
10 touches
10 conflicts
0x454d8940…cfe7
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity