← previous blocknext block →recent activity
Analyzing
Block #84,360,275
26 transactions · 23 stateful · 2026-06-29 00:54:11 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,360,275 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w010w111w012w213w014w215w116w220w121w222w323w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x5581d709…ab77
0x2a68ba…90c5
6 touches
3 conflicts
0xbfe63d66…c3e6
0x34b655…2a6f
6 touches
3 conflicts
0x2f4d415d…5f95
0x34b655…2a6f
5 touches
3 conflicts
0x729c91b8…9538
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity