← previous blocknext block →recent activity
Analyzing
Block #74,258,413
17 transactions · 15 stateful · 2026-05-13 05:36:43 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,258,413 · 17 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
1w03w15w07w18w09w113w214w315w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b5d2e60…99b5
0x34b655…2a6f
8 touches
6 conflicts
0xb9d2cf20…a668
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfe20cb8f…f03d
0x34b655…2a6f
6 touches
3 conflicts
0x9e719c7a…df63
0x34b655…2a6f
5 touches
3 conflicts
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x88e1d863…c925
0x34b655…2a6f
4 touches
1 conflict
0x96d74c73…9553
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x1b5d2e607a…9999b5
Audit this contract →
← previous block·next block →recent activity