← previous blocknext block →recent activity
Analyzing
Block #74,787,351
16 transactions · 15 stateful · 2026-05-15 16:28:02 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,787,351 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ffc25fa…b119
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2f47dcbf…8ac0
0xd32edf…ff58
3 touches
1 conflict
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x47cd2896…f74d
0x065c9d…c394
2 touches
0 conflicts
0x7bbdeed2…49df
0x065c9d…c394
2 touches
0 conflicts
0x976f577b…3916
0x065c9d…c394
2 touches
0 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
1 conflict on slot 0x5ffc25fa7e…57b119
Audit this contract →
← previous block·next block →recent activity