← previous blocknext block →recent activity
Analyzing
Block #74,765,119
39 transactions · 32 stateful · 2026-05-15 13:59:19 UTC
Parallelism
87/100
Blocked
53%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,765,119 · 39 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
1w02w14w06w17w08w110w211w012w113w214w315w416w217w218w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x87e00506…f615
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x116e7d…d8f1
6 touches
3 conflicts
0x00000000…0003
0x116e7d…d8f1
6 touches
3 conflicts
0x65b89141…61de
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0x116e7d…d8f1
6 touches
3 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
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: 0xab35264b…1cfa38
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity