← previous blocknext block →recent activity
Analyzing
Block #70,878,520
31 transactions · 26 stateful · 2026-04-27 14:03:55 UTC
Parallelism
84/100
Blocked
69%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #70,878,520 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w28w09w110w211w312w413w014w115w216w317w325w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
10 touches
10 conflicts
0x8a35acfb…d1b0
0x8d66a4…3095
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x5bbd9ad3…8a32
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x9ac040c1…8223
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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: 0xb857c13a…1a9be1
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity