← previous blocknext block →recent activity
Analyzing
Block #74,774,205
19 transactions · 16 stateful · 2026-05-15 15:00:12 UTC
Parallelism
74/100
Blocked
63%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,774,205 · 19 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
1w02w14w26w17w28w09w110w211w312w414w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x58e06bab…34cd
0x1b6862…e19c
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x1f73e7ef…5b3e
0xd32edf…ff58
5 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