← previous blocknext block →recent activity
Analyzing
Block #74,257,470
12 transactions · 11 stateful · 2026-05-13 05:30:28 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,257,470 · 12 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
1w03w14w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x578e7f66…1b56
0x34b655…2a6f
6 touches
3 conflicts
0xc64ec642…3667
0x34b655…2a6f
4 touches
1 conflict
0x1b9e654e…0a08
0x34b655…2a6f
4 touches
1 conflict
0x5de96bd3…c60c
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x908d4442…2c4b
0x34b655…2a6f
4 touches
1 conflict
0x9df8469b…89b3
0x34b655…2a6f
4 touches
1 conflict
0xc3aacf13…6b3d
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 0x578e7f6639…de1b56
Audit this contract →
← previous block·next block →recent activity