← previous blocknext block →recent activity
Analyzing
Block #74,332,059
34 transactions · 21 stateful · 2026-05-13 13:46:35 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,332,059 · 34 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
2w03w16w010w116w017w118w130w231w332w433w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x20b94f7c…2a9b
0x34b655…2a6f
6 touches
3 conflicts
0x1319ae2c…7f9a
0x34b655…2a6f
4 touches
1 conflict
0x2fe4467b…dd70
0x34b655…2a6f
4 touches
1 conflict
0x313f2565…5b00
0x34b655…2a6f
4 touches
1 conflict
0x57de3828…3fbb
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x6ddcb186…0578
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity