← previous blocknext block →recent activity
Analyzing
Block #70,957,101
28 transactions · 25 stateful · 2026-04-27 22:47:04 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #70,957,101 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w08w210w113w014w015w117w118w219w320w421w523w224w325w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbad68552…e6bf
0x34b655…2a6f
8 touches
6 conflicts
0x95d377b4…fdea
0xd32edf…ff58
7 touches
6 conflicts
0x08943ea2…ed03
0x754704…b603
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0x325b036d…c02a
0x065c9d…c394
5 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
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
6 conflicts on slot 0xbad6855239…f0e6bf
Audit this contract →
← previous block·next block →recent activity