← previous blocknext block →recent activity
Analyzing
Block #74,765,102
36 transactions · 16 stateful · 2026-05-15 13:59:12 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.28
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,765,102 · 36 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
6w09w116w021w022w123w226w132w333w434w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5d70606a…1d53
0x34b655…2a6f
6 touches
3 conflicts
0xfd784183…67bb
0x34b655…2a6f
4 touches
1 conflict
0x36cdae67…8407
0x34b655…2a6f
4 touches
1 conflict
0x388e001a…7e04
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x57de3828…3fbb
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
3 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity