← previous blocknext block →recent activity
Analyzing
Block #74,343,827
21 transactions · 18 stateful · 2026-05-13 15:04:50 UTC
Parallelism
81/100
Blocked
61%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,343,827 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w38w210w011w112w213w314w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0xf3981be5…2c47
0x34b655…2a6f
6 touches
3 conflicts
0xe246df24…3201
0xd32edf…ff58
5 touches
3 conflicts
0xc35da267…ce73
0x065c9d…c394
5 touches
3 conflicts
0xf35dca9e…bd89
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
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
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity