← previous blocknext block →recent activity
Analyzing
Block #84,290,108
40 transactions · 32 stateful · 2026-06-28 17:06:31 UTC
Parallelism
77/100
Blocked
69%
Avg conflicts / tx
1.48
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #84,290,108 · 40 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w16w07w19w210w312w413w014w116w217w318w428w429w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…0002
0xd637b3…4160
10 touches
10 conflicts
0x5df6102c…6494
0xa6afd3…d132
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3f4dc602…5a18
0x34b655…2a6f
8 touches
6 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
6 touches
3 conflicts
0xd2cdfa3f…f071
0x34b655…2a6f
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity