← previous blocknext block →recent activity
Analyzing
Block #74,466,837
17 transactions · 13 stateful · 2026-05-14 04:43:37 UTC
Parallelism
65/100
Blocked
54%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,466,837 · 17 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
4w05w17w08w19w213w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf853eb8e…4027
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x44ad89ba…cf83
0x5c2513…7777
6 touches
3 conflicts
0xce2b6650…ecc3
0x5c2513…7777
6 touches
3 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0xcc67aa…c71c
6 touches
3 conflicts
0x7170c140…36bc
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: Perpl
6 conflicts on slot 0xf853eb8e72…d84027
Audit this contract →
← previous block·next block →recent activity