← previous blocknext block →recent activity
Analyzing
Block #74,789,794
19 transactions · 19 stateful · 2026-05-15 16:44:21 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.89
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,789,794 · 19 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
1w02w03w14w05w06w18w09w110w212w213w314w216w217w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
8 touches
6 conflicts
0x47b807a2…3307
0x065c9d…c394
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x62d6e82b…a750
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x414e9446…4b59
0x34b655…2a6f
4 touches
1 conflict
0x5e13521a…8169
0x34b655…2a6f
4 touches
1 conflict
0x8aa1941d…2988
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 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity