← previous blocknext block →recent activity
Analyzing
Block #74,788,393
29 transactions · 23 stateful · 2026-05-15 16:35:01 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
1.03
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,788,393 · 29 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
1w04w110w211w012w113w214w315w416w519w021w122w223w324w426w328w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0x1ca21f07…e42b
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0x952e5c70…8637
0x065c9d…c394
3 touches
1 conflict
0x0f1bb9b8…eca9
0x065c9d…c394
3 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity