← previous blocknext block →recent activity
Analyzing
Block #84,120,814
39 transactions · 35 stateful · 2026-06-27 22:19:04 UTC
Parallelism
82/100
Blocked
51%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,120,814 · 39 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w39w410w511w012w113w214w315w427w229w531w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0xd637b3…4160
10 touches
10 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x19ce481d…6c36
0x34b655…2a6f
8 touches
6 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
8 touches
6 conflicts
0x5da4ed2f…283f
0xa6afd3…d132
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity