← previous blocknext block →recent activity
Analyzing
Block #74,571,786
18 transactions · 18 stateful · 2026-05-14 16:28:08 UTC
Parallelism
56/100
Blocked
39%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,571,786 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
16 touches
28 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0006
0x2ab50b…5c41
2 touches
0 conflicts
0x039fd5ab…0d4f
0x2ab50b…5c41
2 touches
0 conflicts
0x05b8ccbb…46bc
0x2ab50b…5c41
2 touches
0 conflicts
0x134bb1e3…b524
0x2ab50b…5c41
2 touches
0 conflicts
0x161dd0c3…55e4
0x2ab50b…5c41
2 touches
0 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
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity