← previous blocknext block →recent activity
Analyzing
Block #74,398,612
30 transactions · 26 stateful · 2026-05-13 21:09:26 UTC
Parallelism
83/100
Blocked
54%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,398,612 · 30 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
1w02w04w15w26w37w48w012w113w014w115w216w317w419w121w223w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x73131ffc…b46c
0x5df178…7777
10 touches
10 conflicts
0x00000000…0001
0x2c492d…444e
10 touches
10 conflicts
0x00000000…0000
0x2c492d…444e
10 touches
10 conflicts
0xa472d565…9fe4
0x3bd359…433a
10 touches
10 conflicts
0xc740dd24…9801
0x3bd359…433a
10 touches
10 conflicts
0x44ad89ba…cf83
0x5df178…7777
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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: 0xab35264b…1cfa38
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity