← previous blocknext block →recent activity
Analyzing
Block #84,354,807
42 transactions · 36 stateful · 2026-06-29 00:17:41 UTC
Parallelism
67/100
Blocked
64%
Avg conflicts / tx
1.98
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #84,354,807 · 42 txs across 14 waves · depth 14
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
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w17w28w09w117w018w119w220w321w422w523w625w527w629w130w234w735w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7add284…8d28
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xcffc17bc…3544
0x34b655…2a6f
8 touches
6 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
8 touches
6 conflicts
0x753da1ce…6bbd
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 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
28 conflicts on slot 0xd7add284d9…568d28
Audit this contract →
← previous block·next block →recent activity