← previous blocknext block →recent activity
Analyzing
Block #84,357,973
19 transactions · 18 stateful · 2026-06-29 00:38:48 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,357,973 · 19 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
1w02w112w013w114w215w216w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cdf9369…5331
0x34b655…2a6f
6 touches
3 conflicts
0xda47a23d…57e3
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x13aceb70…cf9f
0x34b655…2a6f
4 touches
1 conflict
0x1b6e8fc2…73d4
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
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 0x0cdf9369de…cb5331
Audit this contract →
← previous block·next block →recent activity